feat(flags): feature-flag control on the project page #5

Open

gabrielvidal wants to merge 1 commits from feature-flags into main

Author	SHA1	Message	Date
Gabriel Vidal	e2bca5c4d6	feat(flags): feature-flag control on the project page Adds a Feature flags card next to the .env editor: it flips each declared flag's for-everyone default in the project's public/feature-flags.json, mints the token link that unlocks the admin panel on the deployed site, and publishes the file to that site with no rebuild. Toggle-only by design — flags are declared in code by whoever ships the feature. The panel on the live site has no Authelia session, so its write comes back to /api/flags/publish with a minted HMAC token, as a text/plain POST so the browser fires no preflight for forward-auth to bounce. Publishing runs on the host sidecar (the container has neither zipgo nor the deploy key) as a fixed one-file operation, never a generic exec. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-17 00:41:29 +02:00

Author

SHA1

Message

Date

Gabriel Vidal

e2bca5c4d6

feat(flags): feature-flag control on the project page

Adds a Feature flags card next to the .env editor: it flips each declared
flag's for-everyone default in the project's public/feature-flags.json, mints
the token link that unlocks the admin panel on the deployed site, and publishes
the file to that site with no rebuild.

Toggle-only by design — flags are declared in code by whoever ships the
feature. The panel on the live site has no Authelia session, so its write comes
back to /api/flags/publish with a minted HMAC token, as a text/plain POST so
the browser fires no preflight for forward-auth to bounce. Publishing runs on
the host sidecar (the container has neither zipgo nor the deploy key) as a
fixed one-file operation, never a generic exec.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-17 00:41:29 +02:00

feat(flags): feature-flag control on the project page #5

1 Commits