This repository was archived by the owner on May 6, 2026. It is now read-only.
ci(fallback): add Filebase IPFS deployment workflow#131
Closed
remiroyc wants to merge 1 commit into
Closed
Conversation
Adds a GitHub Actions workflow that builds the fallback app, uploads it to a Filebase IPFS bucket as a CAR, and publishes the resulting CID to the Site's IPNS so `morpho-fallback-app.myfilebase.site` auto-updates. The existing Fleek workflow is left in place and will be removed in a follow-up PR once Filebase is validated end-to-end. App changes required for IPFS hosting: - `base: "./"` in Vite config so asset paths resolve on path gateways - `VITE_IS_IPFS_BUILD` env flag hides the IPFS info button on IPFS-targeted builds (the button is meaningful only on Vercel) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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
.github/workflows/filebase-deploy.yamlthat, on push torelease, builds the fallback app, uploads it to a Filebase IPFS bucket as a CAR viaipshipyard/ipfs-deploy-action, and publishes the new CID to the Filebase Site's IPNS somorpho-fallback-app.myfilebase.siteauto-updates.fleek-deploy.yaml) untouched — it will be removed in a follow-up PR once Filebase is validated end-to-end. Both pipelines will run in parallel on the next release push.base: "./"inapps/fallback/vite.config.ts— assets resolve correctly on path gateways likeipfs.filebase.io/ipfs/<cid>/...VITE_IS_IPFS_BUILDflag hides the bottom-right "IPFS" info button when the build is IPFS-targeted (the button surfaces alternative IPFS deployments — meaningless when you're already on one)Required repo secrets (new)
Before the first run on
release, add underSettings → Secrets and variables → Actions:FILEBASE_ACCESS_KEY— S3 access key from the Filebase consoleFILEBASE_SECRET_KEY— S3 secret keyFILEBASE_BUCKET— bucket name (morpho-fallback-app)The existing
FLEEK_TOKEN/FLEEK_PROJECT_IDsecrets stay in use for the Fleek workflow.Test plan
bafybeigsuzt4x7cme7lvphp6uzmzmv2r2xou7uvsnhvbdsf6rzodvbewpqrenders the app correctly on the path gateway, IPFS button hidden)FILEBASE_*secrets to the reporelease, verify the workflow succeeds andmorpho-fallback-app.myfilebase.sitereflects the new CID🤖 Generated with Claude Code