Operating
The first staff account
Section titled “The first staff account”Staff get an Admin section in their account menu: an overview, live status of every switcher and the chat service, users and workspaces, plans, chat bots and an audit log.
The first staff account is made in the database. Sign in once, then:
docker compose exec postgres psql -U noalbs noalbs -c \ "UPDATE users SET staff = true WHERE id = (SELECT user_id FROM oauth2_connections WHERE provider_username = 'your_name')"From then on, staff can make others staff under Admin → Users.
Staff don’t get into other people’s workspaces by default: a workspace’s owner or admin grants support access, and everything staff do there is logged.
Every workspace starts on Free. Without billing, staff move workspaces between plans by hand in Admin → Workspaces, and change what each plan allows under Admin → Products. For a copy just for you and your team, raising the Free plan’s limits there is all you need.
To sell plans, NOALBS Cloud uses Stripe: see “Billing” in
deploy/README.md.
Updating
Section titled “Updating”docker compose pull && docker compose up -dThe migrator upgrades the database before the new services start. Migrations only go forward:
to go back to an older version after an update that changed the schema, restore the backup from
before it. Pin a version with NOALBS_TAG=sha-<commit> in .env.
Backups
Section titled “Backups”Back up Postgres (docker compose exec postgres pg_dump -U noalbs noalbs > backup.sql) and keep
.env: without its DATA_ENCRYPTION_KEY, the stored passwords in a backup are useless. NATS only
holds live data (current statuses and the last two minutes of stats) and needs no backup.
Monitoring
Section titled “Monitoring”The services log to stdout (RUST_LOG, LOG_FORMAT=json). With OTEL_EXPORTER_OTLP_ENDPOINT
set they also send logs, traces and metrics to any OpenTelemetry backend, and the repository has a
Grafana dashboard for them (deploy/grafana/noalbs.json). Logs and traces never hold IP
addresses, tokens, stats URLs or chat messages. See “Observability” in deploy/README.md.
Everything else
Section titled “Everything else”deploy/README.md has the
full configuration reference, routing the services through your own proxy, and what each
service needs to reach.