···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 to55 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 no44longer need a secret from the appview to run a knot. All55-authorized commands between services to knots are managed66-via [Service77-Auth](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).55+authorized commands to knots are managed via [Inter-Service66+Authentication](https://atproto.com/specs/xrpc#inter-service-authentication-jwt).87Knots will be read-only until upgraded.98109Upgrading is quite easy, in essence:···1314- `KNOT_SERVER_OWNER` is now required on boot, set this to1415 your DID. You can find your DID in the1516 [settings](https://tangled.sh/settings) page.1616-- Restart your knot once you have replace the environment1717+- Restart your knot once you have replaced the environment1718 variable1819- Head to the [knot dashboard](https://tangled.sh/knots) and1920 hit the "retry" button to verify your knot. This simply···3031 server = {3132- secretFile = /path/to/secret;3233+ owner = "did:plc:foo";3333- .3434- .3535- .3634 };3735 };3836```