veryroundbird.house
1# Migrations
2
3This document is laid out in reverse-chronological order.
4Newer migration guides are listed first, and older guides
5are further down the page.
6
7## Upgrading from v1.8.x
8
9After v1.8.2, the HTTP API for knots has been deprecated and
10replaced with XRPC. Repositories on outdated knots will not
11be viewable from the appview. Upgrading is straightforward:
12
13- Upgrade to latest tag (v1.9.0 or above)
14- Head to the [knot dashboard](https://tangled.sh/knots) and
15 hit the "retry" button to verify your knot
16
17## Upgrading from v1.7.x
18
19After v1.7.0, knot secrets have been deprecated. You no
20longer need a secret from the appview to run a knot. All
21authorized commands to knots are managed via [Inter-Service
22Authentication](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).
23Knots will be read-only until upgraded.
24
25Upgrading is quite easy, in essence:
26
27- `KNOT_SERVER_SECRET` is no more, you can remove this
28 environment variable entirely
29- `KNOT_SERVER_OWNER` is now required on boot, set this to
30 your DID. You can find your DID in the
31 [settings](https://tangled.sh/settings) page.
32- Restart your knot once you have replaced the environment
33 variable
34- Head to the [knot dashboard](https://tangled.sh/knots) and
35 hit the "retry" button to verify your knot. This simply
36 writes a `sh.tangled.knot` record to your PDS.
37
38If you use the nix module, simply bump the flake to the
39latest revision, and change your config block like so:
40
41```diff
42 services.tangled-knot = {
43 enable = true;
44 server = {
45- secretFile = /path/to/secret;
46+ owner = "did:plc:foo";
47 };
48 };
49```
50