ipfs-server_skill

Overview

This skill provides full IPFS node operations: install, configure, run, and maintain an IPFS daemon, manage peers, pin and publish content, and operate gateway services. It focuses on practical commands and configuration snippets for node initialization, storage and network tuning, IPNS publishing, and gateway deployment. Use it to operate production or development IPFS nodes with clear security and maintenance guidance.

How this skill works

The skill inspects node state and repository metrics, issues CLI commands, and guides configuration changes for Addresses, Datastore, Swarm, and Profiles. It covers content lifecycle: adding, pinning, remote pinning, garbage collection, and IPNS publishing. It also explains gateway setup, reverse-proxy integration, monitoring, and private-network construction so you can run and troubleshoot a node end-to-end.

When to use it

• Set up a new IPFS node or migrate configuration to another host
• Publish frequently updated sites via IPNS or manage domain dnslink records
• Run a public or internal HTTP gateway with Nginx or a reverse proxy
• Manage storage, pinning, and remote pinning services to ensure availability
• Configure a private IPFS network or tune performance for high-throughput servers

Best practices

• Keep the API bound to localhost and use a proxy or firewall for multi-user access
• Pin critical content and use remote pinning services for redundancy
• Limit datastore size and schedule GC; test --dry-run before full garbage collection
• Use profiles (lowpower/server) to apply sane defaults for resource constraints
• Protect swarm keys for private networks; treat them as access credentials

Example use cases

• Install and initialize an IPFS node, apply server profile, and expose a local gateway for LAN testing
• Publish a static site: add files, pin the directory, create a custom key, and publish via ipns with dnslink
• Set up remote pinning with Pinata or Web3.Storage and offload long-term availability
• Create a private network by generating a swarm key, removing default bootstrap peers, and starting the daemon
• Deploy a public gateway behind Nginx with rate limiting and monitoring for bandwidth and peers