osmcha-frontend
osmcha-frontend copied to clipboard
Clean up deployment workflow
This PR aims to simplify both development and deploy workflows by making the frontend app easier to run and reducing the differences between what runs in local dev and what gets deployed.
Notable changes:
PUBLIC_URLhas been removed; the frontend is now agnostic to where it gets deployed (meaning it uses domain-less URLS like/static/js/main.12a34bc.jsto fetch required resources). This means you can build one artifact and deploy it anywhere, rather than needing a different artifact for each server you're deploying to (including localhost).- The Docker image now includes a default
nginx.conffile. This file is suitable for production use (though it's HTTP, so it should be used along with a TLS-terminating reverse proxy). In a future PR I'll update the Helm charts in the deploy repo to remove the nginx config file that's inlined there, and use this one instead. - Cleaned up a bunch of old scripts and snippets that were only used when the frontend used to be served from Github Pages.
The changes here go along with some changes to the Django app configuration here: https://github.com/OSMCha/osmcha-django/pull/719