Deploy Static Apps and Websites to IPFS with GitHub Actions

This guide will walk you through the process of configuring GitHub Actions workflow to deploy a repository containing a static app or website to IPFS using the IPFS Deploy Action (https://github.com/ipshipyard/ipfs-deploy-action) developed by the Interplanetary Shipyard team. This video follows all the best practices established as of 2025 and is using open source tooling which avoids lock-in. By the end of this guide, your web app (or just a static website) will be deployed to IPFS automatically when you push to your repository. It will also deploy pull request previews for each commit, and provide some other developer experience features, like commit status updates with the CID of the build, and a comment on pull requests with the IPFS CID and preview links. 00:00 - Introduction to ipfs-deploy-action 01:35 - Prerequisites 02:50 - Getting started with the CID Inspector 03:27 - Adding the ipfs-deploy-action to the project's build workflow 05:37 - Creating the Storacha key and proof (optional if you use Kubo/IPFS Cluster) 08:32 - Trying out the updated workflow with a pull request 10:15 - Preview deployments in pull requests 11:15 - Uploading the build CAR to a Kubo node 11:45 - Side note about securing Kubo RPC with TLS and HTTP Auth 14:12 - Final words 14:52 - Pinata and pinning by CAR vs pinning by CID with the Pinning API Spec 16:03 - You can use this to publish any data or build artefact to IPFS! 16:43 - Wrapping up Links mentioned in the video: The maintainers of the IPFS Deploy Action https://ipshipyard.com/ The Action: https://github.com/ipshipyard/ipfs-deploy-action This guide in text form: https://docs.ipfs.tech/how-to/websites-on-ipfs/deploy-github-action/ https://docs.ipfs.tech/how-to/websites-on-ipfs/static-site-generators/ https://docs.ipfs.tech/how-to/kubo-rpc-tls-auth/