You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rename the Host Env Files to the Fleet's Underscore-Joined Form #550
ptr727/ProjectTemplate#3503 decided the fleet rule for env and secret file names. It covers every such file a repository names, host-side files included. Fields are joined by _, a host name field keeps its hyphens, and the name has no dot except the extension. Blog's host env files, which OPERATIONS.md names as blog.<server>.<environment>.env and deploy/make-release.sh takes as ENV_FILE, become blog_<server>_<environment>.env, with the server field verbatim.
Blocked On
ptr727/ProjectTemplate#3503 step 1, the rule written into the hub's CODESTYLE.md. Blog renames nothing before that merges, so its carried CODESTYLE.md and its docs change together in the resync that carries it.
Done
In that resync, every doc and script naming a host env file uses the new form, and the pull request lists the host-side rename as the maintainer's step on each host. The tracked template .secrets/example.env already conforms.
Unblocked: #556 carries the hub's naming rule into Blog's CODESTYLE.md (hub f60f57d). The maintainer kept the rename out of that carry, so it lands as its own pull request after #556 merges, with the host-side rename as the maintainer's step on each host. #553 pairs with it per its own ordering note.
Landed in develop through #557 (squash b885743), not yet promoted. The four host env files on the maintainer's workstation are renamed to blog_<server>_<environment>.env. Any other host that runs deploy/make-release.sh renames its own files before its next run. This issue closes with the next develop -> main promotion, which lists it.
Activity
ptr727 commentedon Oct 27, 2026
Unblocked: #556 carries the hub's naming rule into Blog's
CODESTYLE.md(hubf60f57d). The maintainer kept the rename out of that carry, so it lands as its own pull request after #556 merges, with the host-side rename as the maintainer's step on each host. #553 pairs with it per its own ordering note.ptr727 commentedon Oct 27, 2026
Landed in develop through #557 (squash
b885743), not yet promoted. The four host env files on the maintainer's workstation are renamed toblog_<server>_<environment>.env. Any other host that runsdeploy/make-release.shrenames its own files before its next run. This issue closes with the next develop -> main promotion, which lists it.