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 between services to knots are managed
6via [Service
7Auth](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).
8Knots will be read-only until upgraded.
9
10Upgrading is quite easy, in essence:
11
12- `KNOT_SERVER_SECRET` is no more, you can remove this
13 environment variable entirely
14- `KNOT_SERVER_OWNER` is now required on boot, set this to
15 your DID. You can find your DID in the
16 [settings](https://tangled.sh/settings) page.
17- Restart your knot once you have replace the environment
18 variable
19- Head to the [knot dashboard](https://tangled.sh/knots) and
20 hit the "retry" button to verify your knot. This simply
21 writes a `sh.tangled.knot` record to your PDS.
22
23## Nix
24
25If you use the nix module, simply bump the flake to the
26latest revision, and change your config block like so:
27
28```diff
29 services.tangled-knot = {
30 enable = true;
31 server = {
32- secretFile = /path/to/secret;
33+ owner = "did:plc:foo";
34 .
35 .
36 .
37 };
38 };
39```