kot.pink
1# Upgrading from v1.7.0
2
3After v1.7.0, knot secrets have been deprecated. You no
4longer need a secret from the appview to run a knot. All
5authorized commands to knots are managed via [Inter-Service
6Authentication](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).
7Knots will be read-only until upgraded.
8
9Upgrading is quite easy, in essence:
10
11- `KNOT_SERVER_SECRET` is no more, you can remove this
12 environment variable entirely
13- `KNOT_SERVER_OWNER` is now required on boot, set this to
14 your DID. You can find your DID in the
15 [settings](https://tangled.sh/settings) page.
16- Restart your knot once you have replaced the environment
17 variable
18- Head to the [knot dashboard](https://tangled.sh/knots) and
19 hit the "retry" button to verify your knot. This simply
20 writes a `sh.tangled.knot` record to your PDS.
21
22## Nix
23
24If you use the nix module, simply bump the flake to the
25latest revision, and change your config block like so:
26
27```diff
28 services.tangled-knot = {
29 enable = true;
30 server = {
31- secretFile = /path/to/secret;
32+ owner = "did:plc:foo";
33 };
34 };
35```