1f912a0f58
Some checks failed
Build Archipelago ISO (dev) / build-iso (push) Has been cancelled
The trusted-registry allowlist in api/rpc/package/config.rs splits the image on '/' and matches the first segment against a fixed set (docker.io, ghcr.io, git.tx1138.com, 23.182.128.160:3000, ghcr.io, localhost). A bare 'bitcoin/bitcoin:28.4' splits to registry="bitcoin" which isn't on the list, so the install RPC was returning 'Invalid Docker image format'. Live catalogs on .160 and gitea-local already hotfixed directly; these static copies keep ISO builds and the final hardcoded fallback in sync. Co-Authored-By: Claude Opus 4.7 (1M context) <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": "git.tx1138.com/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