solid-backoffice

Accounts, permissions and membership for Solid pods: the backoffice from the ecosystem atlas (solid-kit docs/atlas.md).

It replaces pocpod0/backoffice/, which is frozen: it stays deployed until this one covers what it did, and nothing new is added to it.

Kit version: copied from solid-kit at b945ab8 (0.1.0), unchanged in commit 9ed8327. Every divergence from the kit is a diff against that commit.

What it does now

• Before sign-in, a landing that explains pods and collectives. Opened from a collective's invitation link, it speaks for that collective (its name, its folder, and its own title and paragraph when its config.ttl has them) and offers to create an account on our provider first (invite people).
• Signed in, tabs: Home, one tab per collective you run or belong to, and Places (coming). On a phone the tabs move to a bottom bar.
• Home: the collectives you belong to, joining another one from its invitation link, and "You": your name, inbox and agent.
• A collective you belong to: share your folder with its agent (or stop), your membership and how to leave, its members and its agent.
• The collective you run: requests with what each requester's profile says, accept or refuse, the members table, messages it does not understand, and the invitation link to copy.
• Roles and membership are read from the pods at every visit, never stored (membership). Light theme by default, dark one click away.

The protocol underneath is solid-kit ADR 006. What is still to come, in order, is in docs/slices.md.

Adding a collective

The app has no list of collectives. A person sees the ones their profile says they belong to, plus the one they were invited to or typed in. Setting up a collective's pod is done by hand: docs/how-to/set-up-a-collective.md.

All documentation, arranged by kind, starts at docs/README.md; questions go through the FAQ.

Commands

npm install
npm run dev      # the app at /
npm run verify   # typecheck + tests + design audit
npm run test:pods  # the app's code against a throwaway Solid server and test accounts
make             # deploy targets

Sign-in and every write to a real pod are covered only by docs/manual-tests.md, never by npm run verify.

Run from the image

One image for every instance (solid-kit ADR 011). A tag v<version> publishes ghcr.io/nicolasdb/solid-backoffice:<version> (.github/workflows/ci.yml, versions in CHANGELOG.md). An instance is a checkout at that tag, run from instance-template/, which is never edited:

git clone --branch v<version> https://github.com/nicolasdb/solid-backoffice /srv/<instance>
cd /srv/<instance>/instance-template && cp .env.example .env   # then fill it
docker compose pull && docker compose up -d

What an instance brings, all read at run time:

Path in the container	What	From
/instance.json	the login field's default, the sign-up provider (or null), upload limits per server (src/instance.ts)	mounted
/skin.css, /fonts/skin/	the vertical's look, loaded after the kit's theme	mounted
/id.jsonld	the Client ID Document: the consent page names this deploy	written at start from PUBLIC_URL

Absent, the image's defaults hold: pod.nicolasdb.eu's values and the Solid Kit look. The mounts live in the vertical's design-system repo (backoffice/compose.override.yml, loaded through COMPOSE_FILE in .env), not here. The gateway: instance-template/Caddyfile.tmpl, or deploy/gateway-vhost.conf.tmpl for nginx, proxying to <INSTANCE_NAME>-web:80.

An update: git fetch --tags && git checkout v<new>, the same version in .env, then docker compose pull && docker compose up -d.

Not yet on the image: backoffice.nicolasdb.eu and test.nicolasdb.eu still run dist/ behind a stock nginx (docker-compose.yml, make vps-deploy, CI's deploy-test). Moving them is a later step: a checkout at a tag with an .env (no instance.json needed, the defaults are theirs), the gateway vhost pointed at <INSTANCE_NAME>-web, then make vps-push and the rsync deploy go.