archipelagoandClaude Fable 5
dbe37f7ffe
The signed catalog has homed grafana at lfg2025/grafana:10.2.0 in the fleet registry all along; the manifest still pulled Docker Hub's grafana/grafana, so the repo-mismatch guard (correctly) discarded the catalog image on every tick and warned every ~75s on every node. Registry verified to carry the image; aligning the repo path makes the already-signed catalog entry effective — no re-signing needed, no behavioural change beyond pull source. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Archipelago App Catalog
Dynamic app catalog for the Archipelago marketplace. Nodes fetch this catalog to discover available apps.
How it works
- The Archipelago frontend fetches
catalog.jsonfrom this repo - Apps listed here appear in every node's app store automatically
- When a user installs an app, the backend pulls the Docker image and creates the container
Adding a new app
Add an entry to catalog.json:
{
"id": "my-app",
"title": "My App",
"version": "1.0.0",
"description": "What it does",
"icon": "/assets/img/app-icons/my-app.svg",
"author": "Author",
"category": "data",
"dockerImage": "source.archipelago-foundation.org/lfg2025/my-app:1.0.0",
"repoUrl": "https://github.com/...",
"containerConfig": {
"ports": ["8080:8080"],
"volumes": ["/var/lib/archipelago/my-app:/data"],
"env": ["NODE_ENV=production"]
}
}
For apps with hardcoded backend configs (Bitcoin, LND, etc.), containerConfig is optional.
For new apps, include containerConfig so the backend knows how to create the container.
Categories
money, commerce, data, home, nostr, networking, community, development, l484