Repository navigation
Serve our deployment behind the shared front door - #194
Merged
Merged
Conversation
cz-nginx gives up ports 80/443 and TLS to the front door (its own stack) and serves the apex and stats names over the frontdoor network, trusting forwarded client addresses only from that subnet. deploy.sh renders our front door blocks and loads them through its guard. Do It List's block and the old guard leave cz-nginx. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MchCV6T5B393x87E8xonCX
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MchCV6T5B393x87E8xonCX
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 shared front door (its own stack at
/opt/frontdooron the server, owned by neither app) takes ports 80/443 and TLS. Neither app's deploy or mistake can take the other offline.cz-nginxdrops its public ports and certificates and serves behind the front door over thefrontdoornetwork (templates-frontdoor). It trusts forwarded client addresses only from that network's fixed subnet, and its redirects stay relative.deploy.shrenders our front door blocks (docker/production/frontdoor/) and loads them through the front door's guard. A rejected block warns and the last good one keeps serving.doitlist-guard.shleavecz-nginx; the front door loads Do It List's folder itself.Tested locally end to end: redirects, TLS, stats, unknown names rejected, real client address reaching cz-nginx, a broken block from either app turned away while the other keeps serving, live reload, and restart.
Server cutover is a separate step: install the front door, move the ACME webroot and renewal hook, switch
cz-nginx, then update Do It List'sapply-proxy.🤖 Generated with Claude Code
https://claude.ai/code/session_01MchCV6T5B393x87E8xonCX