Add the production deployment tooling - #103
Merged
Merged
Conversation
A two-host layout: the web host runs nginx + the Flask backend; the data host runs Postgres 16, Redis, and the Celery worker/beat. Deploys pull CI-built images tagged by commit SHA rather than building on the hosts, so what runs in production is exactly what CI built. - deploy/: compose files for both hosts, deploy.sh (pins a checkout to a SHA and refuses a dirty tree), restore-and-migrate.sh, nginx.conf, an env template, and a README - docker_push.yml builds and pushes backend+worker images on every green main build; Dockerfile.backend now bakes the code so the image is a self-contained artifact - legacy_data_policy.py: mark migrated legacy filings filed and synthesize their service plans - remove the old build-on-host compose files and prod nginx conf
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A two-host layout: the web host runs nginx + the Flask backend; the data host runs Postgres 16, Redis, and the Celery worker/beat. Deploys pull CI-built images tagged by commit SHA rather than building on the hosts, so what runs in production is exactly what CI built.