parker/cumulus
Watch
1
0
Fork
You've already forked cumulus
 0
Code Pull requests Activity Actions

Keep comments off Forgejo value lines in .env.example #48

Merged
parkerhdavis merged 1 commit from env-example-inline-comments into main 2026-10-12 21:12:24 -06:00
Conversation 0 Commits 1 Files changed 1 +16 -11
parkerhdavis commented 2026-10-12 21:12:21 -06:00 (Migrated from github.com)
Copy link

Summary

The Forgejo variable block in .env.example carried inline comments after each value (FORGEJO_DB_PASSWORD=changeme # openssl rand -hex 32). Copying that block into a host .env made docker compose resolve the values as empty rather than their literal placeholder, so a recreated forgejo container came up with blank secrets and no working configuration. This bit during today's recovery on phd-tower.

Annotations move to comment lines above the values, with an added note that regenerating the secrets mid-life is a rotation — safe only while the forge holds no data.

Verification

  • The phd-tower deploy now uses comment-free value lines and resolves correctly (docker compose config carries every secret at the right length).
## Summary The Forgejo variable block in `.env.example` carried inline comments after each value (`FORGEJO_DB_PASSWORD=changeme # openssl rand -hex 32`). Copying that block into a host `.env` made docker compose resolve the values as **empty** rather than their literal placeholder, so a recreated `forgejo` container came up with blank secrets and no working configuration. This bit during today's recovery on phd-tower. Annotations move to comment lines above the values, with an added note that regenerating the secrets mid-life is a rotation — safe only while the forge holds no data. ## Verification - The phd-tower deploy now uses comment-free value lines and resolves correctly (`docker compose config` carries every secret at the right length).
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
parker/cumulus!48
No description provided.