psa-systems/bunyip
Watch
9
0
Fork
You've already forked bunyip
 0
Code Issues Pull requests Projects Releases 18 Packages Wiki Activity Actions

docs(env): document BUNYIP_COMMUNITY_URL for deployers #316

Merged
longjacksonle merged 1 commit from docs/BUNYIP-329-community-env-example into main 2026-07-02 00:31:30 +02:00
Conversation 0 Commits 1 Files changed 2 +17
longjacksonle commented 2026-07-02 00:22:35 +02:00
Owner
Copy link

What

Follow-up to BUNYIP-329 (#315). BUNYIP_COMMUNITY_URL was wired in config.rs and both compose files, but not in the .env.example templates a deployer copies from, so a teammate bringing up staging/prod would not discover it.

Adds it to:

  • .env.example (root) - the compose-interpolated stack config.
  • bunyip-web/.env.example - the per-var config reference matching src/config.rs.

Both note that empty disables the feature (button hidden) and give the staging/prod example value pointing at the login-init path so the OIDC flow fires immediately.

Docs only; no code change.

## What Follow-up to BUNYIP-329 (#315). `BUNYIP_COMMUNITY_URL` was wired in `config.rs` and both compose files, but not in the `.env.example` templates a deployer copies from, so a teammate bringing up staging/prod would not discover it. Adds it to: - `.env.example` (root) - the compose-interpolated stack config. - `bunyip-web/.env.example` - the per-var config reference matching `src/config.rs`. Both note that empty disables the feature (button hidden) and give the staging/prod example value pointing at the login-init path so the OIDC flow fires immediately. Docs only; no code change.
docs(env): document BUNYIP_COMMUNITY_URL in the .env examples
All checks were successful
E2E / Playwright against deployment (pull_request) Successful in 24s
Details
Check / fmt + clippy + build + tests (pull_request) Successful in 8m53s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
8e2f01ef96 
BUNYIP-329 follow-up. The Community feature flag was wired in config.rs and both compose files but missing from the .env.example templates a deployer copies from, so someone bringing up staging/prod would not discover it. Add it to the root .env.example (compose-interpolated stack config) and bunyip-web/.env.example (the per-var config reference), with the staging/prod example value and a note that empty disables the feature.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
longjacksonle scheduled this pull request to auto merge when all checks succeed 2026-07-02 00:23:53 +02:00
longjacksonle deleted branch docs/BUNYIP-329-community-env-example 2026-07-02 00:31:30 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
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
psa-systems/bunyip!316
No description provided.