finxol.io
+37
-19
content/posts/0-draft-embracing-atproto-pt-2-tangled-knot.md
content/posts/embracing-atproto-pt-2-tangled-knot.md
+37
-19
content/posts/0-draft-embracing-atproto-pt-2-tangled-knot.md
content/posts/embracing-atproto-pt-2-tangled-knot.md
···-Built on atproto, tangled allows you to use your Bluesky identity on a (not quite yet) fully feldged git platform!+Built on atproto, tangled allows you to use your Bluesky/atproto identity on a (not quite yet) fully feldged git platform!···-Bluesky and the AT Protocol are built by a very competent team of well funded engineers working on it for a few years already.+Bluesky and the AT Protocol are built by a very competent team of well funded engineers who've been working on it for a few years already.···It's a "social-enabled git collaboration platform" built for decentralisation, ownership, and social coding.The platform has gained a lot of traction since, and the community is very much involved in the development, but for now tangled is still in alpha.-You can keep ownership of your code, without cutting it off from a popular git platform by running it on a private Gitea or Gitlab server.-The [official docs](https://tangled.sh/@tangled.sh/core/blob/master/docs/knot-hosting.md) give instructions for installation on a NixOS system.+The [official docs](https://tangled.sh/@tangled.sh/core/blob/master/docs/knot-hosting.md) give instructions for installation on a NixOS system,+Luckily, they also provide a community-maintained [Docker install process](https://tangled.sh/@tangled.sh/knot-docker).+At the top of the README that serves as a documentation page, they talk about a pre-built image to use.+I spent way too long trying to debug the parts I control, mainly the Caddy reverse proxy rules.+It turns out the pre-built image was just out of date, and rebuilding it myself fixed it immediately...+I just ran into a slightly stupid version mismatch problem a closer inspection could've revealed earlier.Since it's brand new, there isn't access to the thousands of pre-made reusable Github Actions,···-Just create a new repo on tangled—selecting your knot—set the remote on your local repo, and push to it!-If you specified the knot correctly when creating your repo, it should now live directly on your Knot.+Just create a new repo on tangled—making sure to select your knot, set the remote on your local repo, and push to it!+If you specified the knot correctly when creating your repo, the repo should now live directly on your Knot.<img src="/posts/embracing-atproto-pt2/new-repo.png" alt="Select your new knot when creating a repo" width="80%" style="margin: auto;" />···Since spindles work slightly differently to Github Actions runners, we need to give it a list of dependencies to install.···-Since we don't have access to the existing Github Actions, there's a few sections that needed adapting or manual work.+Since we don't have access to the existing Github Actions, there's a couple sections that needed adapting or manual work.To replace the official Deno Deploy GH Action, we can directly use their `deployctl` cli tool, and give it the appropriate parametres.-I also used this as an excuse to using the `jsr:@std/http/file-server` entrypoint instead of the deno.land url style.+I also used this as an excuse to switch to the `jsr:@std/http/file-server` entrypoint instead of the deno.land url style.···-When pushing to the official knot, the workflow got picked up fine by the official spindle, and showed up in the UI.-When I pushed to my knot however, the official spindle ran the workflow, but it didn't show in the UI.+When pushing to the *official* knot, the workflow got picked up fine by the official spindle, and showed up in the UI.+When I pushed to *my* knot however, the official spindle ran the workflow, but it didn't show in the UI.