A lexicon-driven AppView for ATProto.
happyview.dev
backfill
firehose
jetstream
atproto
appview
oauth
lexicon
docs: expand on post-deploy requirements for Railway deployments
+10
+10
docs/quickstart.md
+10
docs/quickstart.md
···
6
6
7
7
[](https://railway.com/deploy/I1jvZl?referralCode=0QOgj_)
8
8
9
+
### Required configuration
10
+
11
+
After deploying the template, you'll need to configure a few things before the stack works properly:
12
+
13
+
1. **Set your admin DID.** In the AIP service variables, set `ADMIN_DIDS` to your AT Protocol DID (e.g. `did:plc:abc123...`). You can find your DID by looking up your handle on [Internect](https://internect.info/).
14
+
15
+
2. **Generate AIP signing keys.** The `OAUTH_SIGNING_KEYS` and `ATPROTO_OAUTH_SIGNING_KEYS` variables require multibase-encoded P-256 private keys. See the [AIP Signing Keys documentation](https://github.com/graze-social/aip/blob/main/CONFIGURATION.md#signing-keys) for generation instructions.
16
+
17
+
3. **Generate public URLs.** The services won't work until HappyView and AIP have public domains assigned in Railway.
18
+
9
19
## Local development
10
20
11
21
### Prerequisites