···33 A knot ({{range $i, $r := .Registrations}}{{if ne $i 0}}, {{end}}{{ $r.Domain }}{{ end }})
44 that you administer is presently read-only. Consider upgrading this knot to
55 continue creating repositories on it.
66- <a href="https://tangled.sh/@tangled.sh/core/tree/master/docs/migrations">Click to read the upgrade guide</a>.
66+ <a href="https://tangled.sh/@tangled.sh/core/blob/master/docs/migrations/knot-1.7.0.md">Click to read the upgrade guide</a>.
77</div>
88{{ end }}
99
···2233After v1.7.0, knot secrets have been deprecated. You no
44longer need a secret from the appview to run a knot. All
55-authorized commands between services to knots are managed
66-via [Service
77-Auth](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).
55+authorized commands to knots are managed via [Inter-Service
66+Authentication](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).
87Knots will be read-only until upgraded.
98109Upgrading is quite easy, in essence:
···1413- `KNOT_SERVER_OWNER` is now required on boot, set this to
1514 your DID. You can find your DID in the
1615 [settings](https://tangled.sh/settings) page.
1717-- Restart your knot once you have replace the environment
1616+- Restart your knot once you have replaced the environment
1817 variable
1918- Head to the [knot dashboard](https://tangled.sh/knots) and
2019 hit the "retry" button to verify your knot. This simply
···3130 server = {
3231- secretFile = /path/to/secret;
3332+ owner = "did:plc:foo";
3434- .
3535- .
3636- .
3733 };
3834 };
3935```