Skip to content

Deploy tested main builds directly to TigerLift's AWS host - #19

Merged
DIodide merged 1 commit into
mainfrom
fix/automatic-aws-deploy
Nov 20, 2026
Merged

DIodide merged 1 commit into
mainfrom
fix/automatic-aws-deploy

Conversation

@DIodide

@DIodide DIodide commented Nov 20, 2026

Copy link
Copy Markdown
Member

TigerLift's live AWS checkout remained on the old release after feature PRs and build PRs merged. The existing workflow only opened another PR for frontend/dist; it never deployed the server.

This replaces that loop with backend tests, a fresh frontend build, and automatic deployment on main pushes. GitHub uses scoped AWS OIDC credentials and a dedicated SSM document. Releases get isolated virtualenvs, a PostgreSQL backup, explicit migrations, preflight checks, and automatic application rollback if the restarted service fails health checks. The public HTML is compared with the built artifact after deployment.

Database setup and migrations now raise errors so a failed migration cannot produce a successful deployment. The README documents AWS hosting and the new merge-to-deploy flow.

Validation: 13 backend integration tests pass against isolated PostgreSQL; frontend build passes; deployment shell syntax and whitespace checks pass. AWS role, private release bucket, SSM document, and root-owned deployment script are provisioned. Production deployment will run after merge.

@DIodide
DIodide merged commit c810ba3 into main Nov 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant