kubo-deploy-e2e

Deploy a 3-node private IPFS Cluster with Caddy and validate health.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/chinayin/ipfs-artifact-cluster --skill kubo-deploy-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubo-deploy-e2e
Source: https://github.com/chinayin/ipfs-artifact-cluster/tree/main/.claude/skills/kubo-deploy-e2e
Command: npx skills add https://github.com/chinayin/ipfs-artifact-cluster --skill kubo-deploy-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort and guesswork of deploying and validating a private IPFS Cluster (Kubo) infrastructure, ensuring the cluster is fully functional for internal HTML artifact hosting use cases without relying on unverified assumptions.

Core Features & Use Cases

  • Automated Cluster Deployment: Sets up a 3-node private IPFS Cluster with Caddy reverse proxy on a single host using Docker Compose, including automated secret generation and peer configuration.
  • End-to-End Health Validation: Runs automated assertions to confirm 3 peers form correctly, content is replicated across all nodes, gateway rendering works, and failover tolerance is functional when a node goes down.
  • Use Case: Ideal for teams that need to demo, test, or verify a private IPFS Cluster deployment before production use, ensuring multi-replication, private network isolation, and gateway accessibility are all working as expected.

Quick Start

Use the kubo-deploy-e2e skill to automatically deploy a 3-node private IPFS Cluster, run full end-to-end validation tests, and generate a detailed pass/fail report for your infrastructure.

Frequently Asked Questions about kubo-deploy-e2e

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

FAQPage Schema
How do I validate a private IPFS Cluster deployment end-to-end?

You can validate a private IPFS Cluster deployment end-to-end by automating deployment and running health checks that confirm peer formation, content replication, gateway rendering, and failover tolerance, generating a detailed pass/fail report.

What does end-to-end testing for an IPFS Cluster check?

End-to-end testing for an IPFS Cluster checks that 3 peers form correctly, content replicates across all nodes, the gateway renders HTML artifacts, and failover tolerance functions properly when a single node goes down.

How do I deploy a 3-node private IPFS Cluster with Docker Compose?

You can deploy a 3-node private IPFS Cluster with Docker Compose by automating secret generation, peer configuration, and Caddy reverse proxy setup on a single host for internal HTML artifact hosting use cases.

Can I test IPFS Cluster failover tolerance when a node goes down?

Yes, you can test IPFS Cluster failover tolerance when a node goes down by running automated assertions during end-to-end validation to verify that the infrastructure maintains functionality and content availability across remaining nodes.

Does this IPFS Cluster deployment support internal HTML hosting?

Yes, this IPFS Cluster deployment supports internal HTML hosting by using a Caddy reverse proxy to handle gateway rendering, ensuring HTML artifacts are accessible and replicated across the private network.

What are the limitations of testing a single-host IPFS Cluster deployment?

A single-host IPFS Cluster deployment is limited to testing, demonstration, and pre-production verification scenarios, meaning it does not account for multi-host network partitions or real-world distributed infrastructure failover conditions.