···1313 hx-swap="outerHTML"
1414 >
1515 {{ if eq .FollowStatus.String "IsNotFollowing" }}
1616- {{ i "user-round-plus" "size-4 inline group-[.htmx-request]:hidden" }}
1717- {{ i "loader-circle" "size-4 animate-spin hidden group-[.htmx-request]:inline" }}
1818- follow
1616+ {{ i "user-round-plus" "w-4 h-4" }} follow
1917 {{ else }}
2020- {{ i "user-round-minus" "size-4 inline group-[.htmx-request]:hidden" }}
2121- {{ i "loader-circle" "size-4 animate-spin hidden group-[.htmx-request]:inline" }}
2222- unfollow
1818+ {{ i "user-round-minus" "w-4 h-4" }} unfollow
2319 {{ end }}
2020+ {{ i "loader-circle" "w-4 h-4 animate-spin hidden group-[.htmx-request]:inline" }}
2421 </button>
2522{{ end }}
-83
docs/DOCS.md
···502502Note that you should add a newline at the end if setting a non-empty message
503503since the knot won't do this for you.
504504505505-## Troubleshooting
506506-507507-If you run your own knot, you may run into some of these
508508-common issues. You can always join the
509509-[IRC](https://web.libera.chat/#tangled) or
510510-[Discord](https://chat.tangled.org/) if this section does
511511-not help.
512512-513513-### Unable to push
514514-515515-If you are unable to push to your knot or repository:
516516-517517-1. First, ensure that you have added your SSH public key to
518518- your account
519519-2. Check to see that your knot has synced the key by running
520520- `knot keys`
521521-3. Check to see if git is supplying the correct private key
522522- when pushing: `GIT_SSH_COMMAND="ssh -v" git push ...`
523523-4. Check to see if `sshd` on the knot is rejecting the push
524524- for some reason: `journalctl -xeu ssh` (or `sshd`,
525525- depending on your machine). These logs are unavailable if
526526- using docker.
527527-5. Check to see if the knot itself is rejecting the push,
528528- depending on your setup, the logs might be in one of the
529529- following paths:
530530- * `/tmp/knotguard.log`
531531- * `/home/git/log`
532532- * `/home/git/guard.log`
533533-534505# Spindles
535506536507## Pipelines
···15901561Refer to the [jujutsu
15911562documentation](https://jj-vcs.github.io/jj/latest/config/#commit-trailers)
15921563for more information.
15931593-15941594-# Troubleshooting guide
15951595-15961596-## Login issues
15971597-15981598-Owing to the distributed nature of OAuth on AT Protocol, you
15991599-may run into issues with logging in. If you run a
16001600-self-hosted PDS:
16011601-16021602-- You may need to ensure that your PDS is timesynced using
16031603- NTP:
16041604- * Enable the `ntpd` service
16051605- * Run `ntpd -qg` to synchronize your clock
16061606-- You may need to increase the default request timeout:
16071607- `NODE_OPTIONS="--network-family-autoselection-attempt-timeout=500"`
16081608-16091609-## Empty punchcard
16101610-16111611-For Tangled to register commits that you make across the
16121612-network, you need to setup one of following:
16131613-16141614-- The committer email should be a verified email associated
16151615- to your account. You can add and verify emails on the
16161616- settings page.
16171617-- Or, the committer email should be set to your account's
16181618- DID: `git config user.email "did:plc:foobar". You can find
16191619- your account's DID on the settings page
16201620-16211621-## Commit is not marked as verified
16221622-16231623-Presently, Tangled only supports SSH commit signatures.
16241624-16251625-To sign commits using an SSH key with git:
16261626-16271627-```
16281628-git config --global gpg.format ssh
16291629-git config --global user.signingkey ~/.ssh/tangled-key
16301630-```
16311631-16321632-To sign commits using an SSH key with jj, add this to your
16331633-config:
16341634-16351635-```
16361636-[signing]
16371637-behavior = "own"
16381638-backend = "ssh"
16391639-key = "~/.ssh/tangled-key"
16401640-```
16411641-16421642-## Self-hosted knot issues
16431643-16441644-If you need help troubleshooting a self-hosted knot, check
16451645-out the [knot troubleshooting
16461646-guide](/knot-self-hosting-guide.html#troubleshooting).