What's Piri? It's the Provable Information Retention Interface - a Go-based storage node that's part of the Forge network backbone. It works alongside other services like the indexing service and upload service to enable decentralized storage with cryptographic proofs.
Get started with Piri by exploring our comprehensive documentation:
- 🚀 Getting Started - Complete setup guide to deploy Piri
- ⭐️ Best Practices - A checklist of things you should be doing as a Piri node operator
Follow these guides in order to set up Piri:
- Prerequisites - System, network, and Filecoin requirements
- Installation - Download and install Piri
- Key Generation - Create your cryptographic identity
- TLS Configuration - Set up HTTPS for your domains
- Server Setup - Deploy the Piri server
- New to Piri? Start with the Getting Started Guide
Every merge to main publishes ghcr.io/fil-forge/piri:main and dispatches the digest it just
pushed to
infra-nodes.
That workflow rewrites the pin the FilOne Appliance dev node runs and opens a pull request with
auto-merge armed. Merging queues the image; the node picks it up on its next reconcile pass, waits
for a safe proving window, and then restarts.
The dispatch needs two repository credentials: the Actions variable FORGE_BOT_APP_ID and the
Actions secret FORGE_BOT_PRIVATE_KEY, which mint a token scoped to infra-nodes alone. Without
them the publish step fails and the image still lands in GHCR.
All welcome! Piri is open-source. Please feel empowered to open a PR or an issue.
Found a bug or have a feature request? Please open an issue on our GitHub repository.
Dual-licensed under Apache 2.0 OR MIT