Docs: publishing the manifest to fogproject.org is automatic - #14
Merged
Conversation
RELEASING.md landed in #13 telling you to ssh to the website host and pull. That has not been true since 2026-09-07: a */5 cron there runs /usr/local/sbin/fog-version-pull.sh, which pulls and reloads php-fpm only when the pull moved. I copied the instruction out of release-signing-ca.md, which was stale in the same way, so both are fixed here. Confirmed against the live service before changing it: the published manifest carries 0.1.2 through 0.1.6, matching the repo, signed 2026-09-07T16:44:54Z -- so it published with nobody logging in. The step is now "wait, then verify", with a curl that prints the version list rather than the first 200 bytes, because what you actually need to know is whether the new version is in it. The manual pull stays, named as what to do when the cron is the suspect. Also says /version/ is served by nginx as a static file with no PHP in the path, which is a requirement and not an accident: the signature is over exact bytes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CH9HPiM5C6agb3AZxuFAzL
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.
Follow-up to #13, fixing a stale instruction it carried in.
RELEASING.mdstep 3 said to ssh to the website host andgit pull. That has not been true since 2026-09-07 — a*/5cron there runs/usr/local/sbin/fog-version-pull.sh, which pulls and reloads php-fpm only when the pull moved something. I took that line fromdocs/signing/release-signing-ca.md, which was stale in the same way, so both are corrected here.Confirmed against the live service before changing it:
https://fogproject.org/version/agent-stable.jsoncarries0.1.2through0.1.6, matching the repo checkout, signed2026-09-07T16:44:54Z— published with nobody logging in.The step is now "wait, then verify". The verification curl prints the version list rather than the first 200 bytes, because whether the new version is in it is the actual question; and the pull log is quiet on success, so it never proves the cron ran. The manual pull stays, named as what to do when the cron is the suspect.
Also records that
/version/is served by nginx as a static file with no PHP in the path — a requirement, since the signature is over the manifest's exact bytes.Docs only.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CH9HPiM5C6agb3AZxuFAzL