Files

T

spacesopsandClaude Opus 4.7 35c1013520 Build SpacesOps StartOS package (v1.0.0:0)

Initial .s9pk for SpacesOps, targeting StartOS 0.4.0.x with SDK 1.5.1.

- Single managed daemon from spacesops/spacesops:v1.0.0 (x86_64 + aarch64),
  keeping the image entrypoint (/app/docker-entrypoint.sh node server.js).
  Forces PLATFORM_HOST=0.0.0.0 / PLATFORM_PORT=7264 so the StartOS proxy can
  reach the app. Single `ui` interface on 7264.
- Depends on the Spaces service (>=0.0.9:3) and auto-wires the spaced RPC creds:
  main.ts mounts the Spaces `main` volume read-only at /spaces-data, execs a
  read of its store.json inside the subcontainer, and injects SPACED_RPC_USER/
  PASSWORD + SPACED_RPC_URL=http://spaces.startos:7225. Throws to retry until
  Spaces is installed and seeded.
- Generates a Nostr operator keypair (nostr-tools, bundled by ncc) and a strong
  session secret in idempotent init tasks (.once() reads, allowWriteAfterConst
  merges). Actions: show-operator-credentials, import-operator-key,
  show-admin-credentials (surfaces the fixed admin/Whatever! login with a
  warning), configure-platform (optional relay/mode/CoinGecko/SUBSD).
- Install alert warns to install Spaces first and about the fixed admin
  credential. Backs up the `main` volume.
- Icon: icon.svg (source spacesops.svg). The `spaces` dependency uses
  assets/spaces-icon.png for its Marketplace metadata.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-26 10:28:18 -04:00

2.0 KiB

Raw Blame History

SpacesOps

SpacesOps is a web platform for confirming Spaces ownership and selling subspace names. It connects to the Spaces spaced daemon, signs operator events on Nostr, and optionally adds pricing and subname-purchase features.

Before you start: install Spaces

SpacesOps requires the Spaces service. Install Spaces from the Marketplace and let it sync before using SpacesOps. SpacesOps connects to it automatically — you do not need to enter any spaced RPC credentials. Until Spaces is installed and its credentials are ready, SpacesOps will keep restarting; this is expected.

First run

On install, StartOS automatically:

Generates a Nostr operator keypair that SpacesOps signs events with.
Generates a strong session secret.

There is no setup wizard. Once Spaces is reachable, open the Web UI from the SpacesOps dashboard.

⚠️ Admin credentials — important

The admin area is protected by a fixed, well-known login that is baked into the image and cannot be changed:

Username: admin
Password: Whatever!

The Show Admin Credentials action displays these. Because the admin area can run SQL and manage tenants, keep this service private — use it over Tor or your LAN, and do not expose its admin routes to the public internet.

Actions

Show Operator Credentials — view your Nostr operator npub, nsec, and hex keys.
Import Operator Key — replace the operator keypair with one you provide (a 64-character hex secret key). This changes your operator identity and restarts the service.
Show Admin Credentials — view the fixed admin login (with the warning above).
Configure Platform — optionally set the Nostr relay, theme mode, CoinGecko pricing, and a SUBSD backend. Pricing and subname-purchase features stay off until you configure them here. Saving restarts the service.

Backups

Backing up SpacesOps captures everything under /data — all databases, signed artifacts, your operator keypair, and your settings.

2.0 KiB Raw Blame History