Harden application, database, and deployment security - #150
Merged
Conversation
vezcode
force-pushed
the
vezi/full-production-hardening
branch
from
August 9, 2026 19:09
b3a2963 to
1df8903
Compare
vezcode
marked this pull request as ready for review
August 9, 2026 19:13
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.
What changed
Why
The production review found active dependency advisories, CI exceptions for those advisories, shared database credentials, unnecessary network exposure, a fail-open production configuration, stale public migrations and retention gaps.
Verification
Deployment note
Apply
deploy/hetzner/migrations/20260809210000_anonymize_withdrawn_newsletter.sqlafter a verified backup. Configure differentAPI_DATABASE_URLandPOSTGREST_DATABASE_URLcredentials before removing the documented compatibility fallback.