Put FN_FUNDING_MANIFESTS in the compose the repository ships #261

2026-10-15T22:58:08Z

extant2000git commented

2026-10-15 22:58:08 +00:00

The route landed in #259 and the variable went into the box compose by hand, because a deploy alone did not pick it up: docker-compose.prod.yml lists every variable explicitly under environment: and interpolates from .env, so a variable present only in .env reaches the container not at all. The relay restarted from the new image and still answered 404 until the compose named it.

That left the only copy on the box, one deploy away from being dropped, and the FLOSS/fund listing depends on the path it enables: without it https://flamenetmessenger.com/.well-known/funding-manifest-urls 404s and the entity and webpage URLs in the manifest go unverified.

Now the repository carries it and .env.example documents it.

Gates run locally: configuration doc 105 variables all documented, secret sweep clean, 9 generated pages match their sources, swift build complete.

🤖 Generated with Claude Code

The route landed in #259 and the variable went into the box compose by hand, because a deploy alone did not pick it up: `docker-compose.prod.yml` lists every variable explicitly under `environment:` and interpolates from `.env`, so a variable present only in `.env` reaches the container not at all. The relay restarted from the new image and still answered 404 until the compose named it. That left the only copy on the box, one deploy away from being dropped, and the FLOSS/fund listing depends on the path it enables: without it `https://flamenetmessenger.com/.well-known/funding-manifest-urls` 404s and the entity and webpage URLs in the manifest go unverified. Now the repository carries it and `.env.example` documents it. Gates run locally: configuration doc 105 variables all documented, secret sweep clean, 9 generated pages match their sources, swift build complete. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

extant2000git added 1 commit 2026-10-15 22:58:09 +00:00

Put FN_FUNDING_MANIFESTS in the compose the repository ships

ci / swift (pull_request) Successful in 9m5s

Details

ci / checks (pull_request) Successful in 14s

Details

ci / image (pull_request) Successful in 51s

Details

ci / deploy (pull_request) Skipped

Details

1dc4d1b713

The route landed in #259 and the variable went into the box's compose by hand,
because a deploy alone did not pick it up: this file lists every variable
explicitly under environment: and interpolates from .env, so a variable present
only in .env reaches the container not at all. The relay restarted from the new
image and still answered 404 until the compose named it.

That left the only copy on the box, one deploy away from being dropped, and the
FLOSS/fund listing depends on the path it enables. Now the repository carries it
and .env.example documents it, so a fresh clone and a rebuilt compose both keep
working.

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

extant2000git merged commit 91af917aa4 into main

2026-10-15 23:08:21 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#261