atproto pds in zig
pds.zat.dev
pds
atproto
Document invite token env workflow
+9
-5
+3
-1
AGENTS.md
+3
-1
AGENTS.md
···
72
72
zig zen
73
73
```
74
74
75
-
Use `just invite` for admin-minted invite codes and `just bench ...` for local
75
+
Use `just invite` for admin-minted invite codes. Assume `ZDS_ADMIN_TOKEN` is
76
+
set in the repo `.env`; source it before running the target, for example
77
+
`set -a; . ./.env; set +a; just invite`. Use `just bench ...` for local
76
78
performance probes. Keep commits small. Amend only when asked. Do not revert
77
79
user or sibling-repo changes unless asked.
+6
-4
docs/invite-codes.md
+6
-4
docs/invite-codes.md
···
47
47
requests cannot both consume a one-use code.
48
48
49
49
When invite-required mode starts against an empty database, ZDS creates one
50
-
bootstrap code and logs it. After that, mint codes through the XRPC endpoint:
50
+
bootstrap code and logs it. After that, mint codes through the XRPC endpoint.
51
+
For local admin operations, assume `ZDS_ADMIN_TOKEN` is set in the repo `.env`
52
+
and source it before running the Just target:
51
53
52
54
```sh
53
-
ZDS_ADMIN_TOKEN='...' just invite https://pds.zat.dev
55
+
set -a; . ./.env; set +a; just invite https://pds.zat.dev
54
56
```
55
57
56
58
For a multi-use code:
57
59
58
60
```sh
59
-
ZDS_ADMIN_TOKEN='...' just invite https://pds.zat.dev 3
61
+
set -a; . ./.env; set +a; just invite https://pds.zat.dev 3
60
62
```
61
63
62
64
For a code assigned to a specific DID:
63
65
64
66
```sh
65
-
ZDS_ADMIN_TOKEN='...' just invite https://pds.zat.dev 1 did:plc:...
67
+
set -a; . ./.env; set +a; just invite https://pds.zat.dev 1 did:plc:...
66
68
```
67
69
68
70
## reference notes