Refreshing pages does not work

[K20shores]

Refreshing on pages that aren't the home page results in a 404

Acceptance Criteria

• On any route that isn't the home (e.g., /LoggedIn), refreshing the page will load that page

Ideas

• Figure out how to configure react-router-dom to load the page on a refresh

[LucientZ]

The refreshing appears to work both when running both the development server and preview build locally (eg. npm run dev or npm run build && npm run preview).

It looks like this stackoverflow discussion details why this is the case. Switching over to a <HashRouter> skips the issue altogether, but it turns the actual site into a single page site which I don't think is what we want since other pages should be searchable via web browsers.

@K20shores Are there any details as to how the site is hosted in production?

[K20shores]

@LucientZ, yes. We self host a machine in ACOM. This machine hosts the web files, the API server compiled to run directly on our hardware which is setup as a linux server, and a service running the database. Nginx routes all of our traffic.

If this works in dev, then it's most likely a deployment issue and something that could be fixed by messing with the nginx configuration.

Thanks for investigating this. Once y'all get a few PRs in, we can deploy your changes and revisit this issue then. Sound like a plan?