fix(deploy): support bounded deployment on a restricted production host - #61
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
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.
Production deployments now use a configurable restricted host/account, fixed CPU and memory limits, and a four-connection PostgreSQL pool. The host performs a verified encrypted off-host backup before migrations through a no-argument maintenance hook. Existing blue/green rollout and rollback gates remain.
The required dependency audit also exposed baseline advisories; targeted compatible security overrides reduce the full audit to zero findings.
Validation: formatting, typecheck, build, 61 unit tests, 37 endpoint tests, eight deployment contract tests on Linux, shell syntax checks, and dependency audit.