Repository navigation
Deploy tested main builds directly to TigerLift's AWS host - #19
Merged
Merged
Conversation
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
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.
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.