archipelagoandClaude Opus 5
8e814ca06a
Demo images / Build & push demo images (push) Failing after 2m22s
Replaces the registry host across 86 files: 309 references, covering all 40 app manifests, the orchestrator and container crates, the release and catalog scripts, both demo-images workflows, the ISO builder, demo-deploy, and the frontend marketplace data. Verified the domain actually serves the registry before rewriting anything, rather than assuming the web host implies the registry: - TLS verifies clean, HTTP/2 on the web root - an anonymous token grants a manifest fetch (HTTP 200) with no credentials - skopeo inspect --no-creds resolves an image and lists its tags That last check is the one that matters: an outside developer with no account can now pull, which was the functional blocker for publishing at all. Plain-HTTP references become HTTPS in the same pass, so OTA downloads stop crossing the network in the clear. Deliberately NOT rewritten: - The public FIPS anchor on port 8444. It is a functional network endpoint every node dials to bootstrap the mesh — closer to Bitcoin Core's hardcoded seeds than to leaked infrastructure. The domain does resolve to the same host, so it could become a hostname, but that adds a DNS dependency to the path used precisely when things are broken. Worth a deliberate decision, not a side effect of this change. - The companion APK on port 2100. The domain returns 404 for that path, so rewriting it would swap a working URL for a broken one. The Releases page does serve (200), which is where the plan already wants those binaries. - releases/app-catalog.json, releases/manifest.json and release-manifest.json. These carry `signature` and `signed_by`; editing their contents invalidates the signature and the fleet refuses artifacts that fail verification. They were rewritten in a first pass and reverted — they must be regenerated and re-signed through the signing ceremony instead, which needs the mnemonic. So the catalog still advertises the old host until that ceremony runs. Nodes resolve images through the signed catalog, not the on-disk manifests, so this commit alone does not change what a node pulls. Verified: archipelago-container 75/75; every manifest still parses with a top-level app block; no signed artifact modified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Archipelago — Public Demo deploy
A click-to-play demo of the Archipelago UI, backed entirely by a mock backend.
Every visitor gets an isolated, ephemeral sandbox (own apps, wallet, files),
real container runtimes are never touched, and Bitcoin runs on signet test
coins. Login password: entertoexit (shown on the login screen).
This directory is the full contents of the public archy-demo repo. It holds no
source — only this compose file that pulls prebuilt :demo images.
Deploy in Portainer
- Stacks → Add stack → Repository (or paste
docker-compose.ymlinto the web editor). - Set environment variables (see
.env.example) — at minimumREGISTRY, andANTHROPIC_API_KEYif you want the AI chat panel. - Deploy. The UI is served on
:2100(override withDEMO_WEB_PORT).
To pick up a new build, redeploy the stack (or wire the CI Portainer webhook).
How it stays current
The images are built from the Archipelago monorepo by
.github/workflows/demo-images.yml on every change to neode-ui/, tagged :demo
and :<git-sha>, and pushed to REGISTRY. Editing the real UI → CI rebuilds →
redeploy here. No source lives in this repo.
What's mocked
- Per-visitor isolation — state keyed by a
demo_sidcookie, idle-reaped. - Apps — install/uninstall/start/stop are simulated (no real Docker).
- Wallet/Bitcoin — signet-flavored; use the in-UI faucet for test sats.
- Files — real per-session upload/rename/delete, 50 MB quota, wiped on reap.
- Intro — replays once per calendar day per browser.