Repository navigation
Serve versioned web releases without restarting application services - #15
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9155347ae4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if not (root / "index.html").is_file(): | ||
| raise ValueError("Extract an initial web release into this directory before migrating") | ||
|
|
||
| sources = [path for path in root.iterdir() if path.name != "releases" and not path.name.startswith(".")] |
There was a problem hiding this comment.
When an existing flat deployment contains publicly served dot-prefixed content such as .well-known/assetlinks.json, this filter silently omits the entire entry even though the previous /srv/web root served it. After Caddy switches to current, requests for those files fall through to /index.html, breaking domain verification or app-link association; copy dot-prefixed public assets and exclude only specific migration-control or private artifacts.
Useful? React with 👍 / 👎.
Serve the web app through an atomic
currentsymlink and preserve deployed files during the initial layout migration. Keep deployment validation aligned with the new layout and document restricted web delivery and rollback without restarting API, PowerSync or database services.Validation:
The server version stays unchanged in this implementation PR. The coordinated release will include the goal-tracking changes already on development and must deploy the server before the client.