skills.rest
ccashwell
ccashwellCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ipfs-deployment

Automate dApp frontend deployment to IPFS with pinning and ENS content hashes.

120|12|Updated Apr 10, 2026
Search Tags:#deployment#gateway#ens#ipfs#pinata#ipfs-pinning#fleek
One-click install
npx skills add https://github.com/ccashwell/evm-cortex --skill ipfs-deployment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ipfs-deployment
Source: https://github.com/ccashwell/evm-cortex/tree/main/skills/ipfs-deployment
Command: npx skills add https://github.com/ccashwell/evm-cortex --skill ipfs-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying dApp frontends to IPFS and decentralized hosting can be challenging due to static build requirements, pinning strategies, content addressing, and gateway configuration. This skill consolidates best practices and practical steps to ensure permanence and censorship resistance.

Core Features & Use Cases

  • Static build readiness for IPFS-compatible hosting across Next.js, Vite, and Create React App.
  • IPFS pinning workflows with Pinata and Fleek, plus content hash integration via ENS.
  • Gateway configuration and verification to ensure reliable access through public and custom gateways.
  • CI/CD integration and deployment checks to produce repeatable, verifiable releases.
  • Use Case: Deploy a new frontend version to IPFS, pin it to multiple services, update ENS content hash, and validate access via gateways.

Quick Start

Deploy your latest build to IPFS and verify accessibility across multiple gateways.

Frequently Asked Questions about ipfs-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a dApp frontend to IPFS using Pinata or Fleek?▼

Deploying a dApp frontend to IPFS involves configuring static builds for frameworks like Next.js or Vite, pinning the output via Pinata or Fleek, and verifying accessibility through configured gateways.

How do I update an ENS content hash after pinning my static site to IPFS?▼

Updating an ENS content hash after IPFS pinning involves retrieving the generated content identifier and mapping it to your ENS name to resolve decentralized frontend access.

Does IPFS deployment support static sites built with Vite and Create React App?▼

IPFS deployment supports static site frameworks including Vite, Create React App, and Next.js, handling static build requirements and trailingSlash configuration for IPFS-compatible hosting.

How do I automate IPFS pinning and gateway verification in a CI/CD pipeline?▼

Automating IPFS pinning and gateway verification in CI/CD pipelines involves integrating deployment checks that pin builds to Pinata or Fleek and validate access through gateways for repeatable releases.

What is the best way to configure trailingSlash for Next.js builds hosted on IPFS?▼

Configuring trailingSlash for Next.js builds on IPFS requires adjusting static build settings to ensure consistent routing and content addressing across decentralized gateways.

Related Skills

Explore More Software Engineering Skills→
collat-labscollat-labs
1

frontend-playbook

Guide Ethereum dApp frontend teams through Next.js/Scaffold-ETH2 production deployment.

Official
Advanced
mashharukimashharuki

frontend-playbook

Automate Ethereum dApp frontend deployment to IPFS or Vercel with ENS content-hash updates.

Community
Advanced
obulaiobulai
1

obul-pinata

Pin files to public and private IPFS networks via Obul proxy.

Official
Intermediate
freeslugsfreeslugs

frontend-playbook

Deploy Ethereum dApps to production via IPFS and Vercel.

Community
Advanced