Developers
Running Off the Clock
One community needs an identity on a PDS with permissioned spaces, three small services, and three domain names.
What you need
Draft outline
- A community identity (
did:plc) on a PDS that supports permissioned spaces and managing-app policies (today: atproto-crates' PDS, as on vesuvius). - Three hostnames: the site,
api.andfeeds., each with TLS, since the services aredid:web. - Somewhere to run three containers, each with a small persistent volume (SQLite).
- Optional: a geocoder, map tiles, an embeddings API, VAPID keys for push. See Optional features.
The steps
Draft outline
- Generate keys (
scripts/gen-keys.shorjust keys). - Configure each service (Configuration).
- Deploy and point the domains (Deploying).
- Wait for each service's
/_ready. - Sign in as the community identity: setup mode creates the self management space, then "Create your first space" makes general.
- Connect the community session; make your first community admin.
- Publish the lexicons and
_lexiconrecords.
Trying it locally
Draft outline
The integration rig (tools/rig, docs/integration.md) runs a PLC, PDSes, and all three services with fixtures, behind a tunnel.