Part of the federated-master roadmap (Stage A: full backend stack on box #2; see functionland/pinning-service#46).
The prod fula-gateway image has no committed build recipe — the federated-master installer (pinning-service update-scripts/join-as-master.sh, gateway compose profile) needs a reproducible image any whitelisted operator can build.
Ships: docker/Dockerfile.gateway — multi-stage build of the fula-gateway bin (cargo build --release -p fula-cli --bin fula-gateway) on rust:1-bookworm, slim Debian runtime, env-driven config (FULA_HOST/FULA_PORT/IPFS_API_URL/CLUSTER_API_URL/PINNING_SERVICE_ENDPOINT/STORAGE_API_URL/JWT_SECRET/FULA_PIN_QUEUE_PATH...). No behavior changes to the gateway itself.
Verify (e2e): image builds on a clean Ubuntu 24.04 box; container serves the S3 API on :9000 against the box's kubo+cluster writer; join-as-master.sh auto-enables the gateway profile when the image exists.
🤖 Generated with Claude Code
Part of the federated-master roadmap (Stage A: full backend stack on box #2; see functionland/pinning-service#46).
The prod
fula-gatewayimage has no committed build recipe — the federated-master installer (pinning-serviceupdate-scripts/join-as-master.sh, gateway compose profile) needs a reproducible image any whitelisted operator can build.Ships:
docker/Dockerfile.gateway— multi-stage build of thefula-gatewaybin (cargo build --release -p fula-cli --bin fula-gateway) on rust:1-bookworm, slim Debian runtime, env-driven config (FULA_HOST/FULA_PORT/IPFS_API_URL/CLUSTER_API_URL/PINNING_SERVICE_ENDPOINT/STORAGE_API_URL/JWT_SECRET/FULA_PIN_QUEUE_PATH...). No behavior changes to the gateway itself.Verify (e2e): image builds on a clean Ubuntu 24.04 box; container serves the S3 API on :9000 against the box's kubo+cluster writer; join-as-master.sh auto-enables the gateway profile when the image exists.
🤖 Generated with Claude Code