Repository navigation
Deploy the website independently on Hetzner - #3
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Website deployment currently writes inside the app server directory. Give the landing page its own papyrus-website Compose project and /srv/apps/papyrus-website/site release directory on the same Hetzner VM. The website container joins only the external edge network, publishes no host ports, and remains independent of app service restarts. The shared proxy handles public HTTPS; the existing version-triggered workflow continues to atomically activate content through the dedicated upload account.
Validation: seven focused automation tests and the static build passed. Compose project/network separation was checked. The upload, activation, identical-archive retry, and public revision were verified against Hetzner; all container IDs remained unchanged during website deployment. No app test suite was run.
Merge this PR, then manually run Website release on master for the initial website release. The SSH environment is already configured. Subsequent website version increases deploy automatically.