refactor(env): unify env var prefixes under FORGEJO_ and FORGEJO_MCP_ #64
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/FJ-49-unify-env-var-prefixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rename the build-metadata
FJ_*variables toFORGEJO_*and the bare, un-namespaced MCP runtimeMCP_*variables toFORGEJO_MCP_*so every environment variable thefjbinary reads lives under a singleFORGEJO_namespace. The bareMCP_*prefix could collide with any other MCP server sharing the process environment;FORGEJO_MCP_*removes that hazard.Build metadata (baked outputs in build.rs, read via option_env! in version.rs): FJ_GIT_SHA/FJ_BUILD_DATE/FJ_COMMIT_DATE/FJ_TRAIN -> FORGEJO_; the un-prefixed build-arg inputs GIT_SHA/COMMIT_DATE/BUILD_DATE are unchanged. Runtime FJ_FALLBACK_HOST -> FORGEJO_FALLBACK_HOST in repo.rs. MCP runtime MCP_TRANSPORT/MCP_HTTP_ADDR/MCP_HTTP_TOKEN/MCP_ALLOW_EDIT/MCP_ALLOW_DELETE/MCP_ALLOW_GLOBAL_WRITE/MCP_ENDPOINT -> FORGEJO_MCP_ across fj-mcp and fj, including render_unit's baked systemd Environment= lines and its unit-file tests.
Also updates the workflows, Dockerfiles, localization .ftl files, README.md, and CLAUDE.md, and documents the breaking change (a systemd unit written by an older
fjstill names MCP_* and must be regenerated withfj mcp service install) in the README release note and thefj mcp service installhelp text.#FJ-49