ci(pinner): align with Filebase migration in ewm-das#292
Merged
Conversation
Upstream ewm-das #72 replaced the w3 CLI integration with a direct-HTTPS Filebase client (FILEBASE_RPC_TOKEN, env-only). The new pinner listens only on :5080 and no longer accepts --w3-agent-key / --w3-delegation-proof-path. bsp-agent (the upstream producer) has been migrated in covalenthq/bsp-agent#341; this PR brings refiner's three compose files, the docker-ci-test workflow, and the .env*/.envrc defaults into line so refiner can keep consuming from the unified pinner. Refiner's Elixir code already configures the pinner via IPFS_PINNER_URL (config/{config,docker,test}.exs already default to :5080), so no application changes are needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…-das Sweeps README, ARCH, DEVELOPMENT, and the rudder-compose.service unit: - W3_AGENT_KEY / W3_DELEGATION_FILE / WEB3_JWT exports and prose → FILEBASE_RPC_TOKEN (Filebase IPFS RPC API token, scoped per bucket). - ipfs-pinner / :3001 → ewm-das / :5080 across all example envs and logs. - Replace the "Web3.storage + Pinata + dweb.link" pinner blurb with a description of the new Filebase-backed ewm-das pinner. - Drop the now-meaningless `echo web3-jwt: $WEB3_JWT` line from the CI proof-chain entrypoint. - Stale w3s.link gateway log examples replaced with a generic "fetching cid" line — the new pinner serves through Filebase's dedicated gateway + DHT, not w3s.link. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Temporary swap so CI exercises the freshly-built ewm-das image (which replaces the internal IPFS gateway set). Will revert to :stable before merge once the run goes green.
mix.exs was lagging the git tags (0.6.1 internally while git is on v0.7.0). Bumping to 0.8.0 to match the upcoming release that ships the Filebase pinner migration.
noslav
force-pushed
the
migrate-pinner-to-filebase
branch
from
239b00c to
7de8503
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upstream ewm-das#72 replaced the w3 CLI integration with a direct-HTTPS Filebase client. The new pinner is
FILEBASE_RPC_TOKEN-only (env), listens only on:5080, and no longer accepts the--w3-agent-key/--w3-delegation-proof-pathflags. bsp-agent has been migrated in covalenthq/bsp-agent#341 — this PR brings refiner's compose / CI / env defaults into line so it can keep consuming from the unified pinner.docker-compose-ci.yml— swapW3_*env +--w3-*pinner flags forFILEBASE_RPC_TOKEN; drop port3001fromexpose:andports:; fix$PROOF_OUT_HEXshell-escaping inside the entrypoint heredoc.docker-compose-mbase.yml,docker-compose-mbeam.yml— same env + pinner-flag changes (no port 3001 was exposed in these)..github/workflows/docker-ci-test.yaml— removeWEB3_JWT,W3_AGENT_KEY,W3_DELEGATION_FILEfrom the generated.env; addFILEBASE_RPC_TOKEN..env_example— drop the staleWEB3_JWTline + comment; update bothIPFS_PINNER_URLdefaults from:3001to:5080and the docker hostname fromipfs-pinnertoewm-das..envrc—IPFS_PINNER_URLport:3001→:5080.The Elixir code is already abstracted via
Application.get_env(:refiner, :ipfs_pinner_url), andconfig/{config,docker,test}.exsalready default to port:5080. No application changes needed.Required CI setup (out of band)
The
FILEBASE_RPC_TOKENrepo secret needs to be added under Settings → Secrets and variables → Actions ofcovalenthq/refinerbefore CI will pass. The retiredWEB3_JWT,W3_AGENT_KEY, andW3_DELEGATION_FILEsecrets can be deleted once this PR merges.Test plan
FILEBASE_RPC_TOKENto repo secretsdocker-ci-test—ewm-dascontainer reachesStarting server on :5080, the threecurl -Fuploads at/uploadreturn 200, andrefinerexits 0 aftercoveralls.jsondocker inspect refiner(already in workflow)mbase/mbeamdeployments: setFILEBASE_RPC_TOKENin operator env and confirm autoheal-monitored ewm-das stays up🤖 Generated with Claude Code