Configure IPFS HTTP gateways with origin isolation, CORS, and rate-limiting.
npx skills add https://github.com/MysticRyuujin/spirens --skill gateways
Please help me install this Agent Skill. Skill: gateways Source: https://github.com/MysticRyuujin/spirens/tree/main/gateways Command: npx skills add https://github.com/MysticRyuujin/spirens --skill gateways
IPFS gateways can expose content with varying isolation, security, and performance characteristics. This Skill guides you through choosing between path-based and subdomain gateways, trusted vs trustless responses, CORS handling, and rate-limiting strategies to avoid public gateway abuse.
Configure a per-CID subdomain gateway and test access to a sample IPFS content to validate origin isolation and CORS settings.
High-intent search queries and answers about installing and using this skill.
Configure an IPFS gateway for secure content exposure by choosing between path-based or per-CID subdomain deployments, setting up TLS termination with wildcard certificates, and applying CORS rules. This ensures proper origin isolation and safe HTTP access.
Path-based IPFS gateways serve content from a single origin, limiting browser origin isolation, while subdomain gateways assign each CID a unique subdomain. Subdomain gateways provide stronger origin isolation and maintain link validity for web applications.
Trusted IPFS gateway responses rely on the gateway to verify content authenticity, whereas trustless responses allow clients to independently verify content using cryptographic proofs. Trustless gateways ensure end users can validate the data without gateway trust.
Set up CORS and rate-limiting for a public IPFS gateway by configuring HTTP response headers for cross-origin access and applying request rate limits. These strategies prevent public gateway abuse while allowing controlled external access.
Yes, wildcard certificates are required for TLS termination on subdomain gateways. Because per-CID subdomain gateways dynamically generate hostnames for each content identifier, a wildcard certificate secures all dynamically created subdomains.
Avoid using a public IPFS gateway when serving private or restricted content without strict access controls, or when origin isolation is critical but only a path-based gateway is available. Public gateways lack rate-limiting and access restrictions by default.
ccashwellAutomate dApp frontend deployment to IPFS with pinning and ENS content hashes.
FlorianRiquelmeImplement global error handling with retry logic and user-friendly messages.
renneConfigure Traefik for HTTPS with automatic Let's Encrypt certificate management.
MysticRyuujinConfigure IPFS nodes for content addressing, pinning, and peering.
