-
+
diff --git a/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/index.html b/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/index.html
index 94bd76b2..3569630b 100644
--- a/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/index.html
+++ b/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/index.html
@@ -10,7 +10,6 @@
-
@@ -182,8 +181,8 @@ log:
servers:
- url: "http://gitea:3000"
-
Something to consider is whether or not you want to use ssh with git. One method of getting this to work with containers is to use ssh container passthrough. I decided to keep it simple and not use ssh, since communicating over https is perfectly fine for my use case.
-
After adding the above configuration, running docker compose up -d
should be enough to get an instance up and running. It will be accessible at https://gitea.my-tailnet-name.ts.net from within your tailnet.
+
Something to consider is whether or not you want to use ssh with git. One method to get this to work with containers is to use ssh container passthrough. I decided to keep it simple and not use ssh, since communicating over https is perfectly fine for my use case.
+
After adding the above configuration, running docker compose up -d
should be enough to get an instance up and running. It will be accessible at https://gitea.my-tailnet-name.ts.net from within the tailnet.
Connecting a Runner#
I installed the runner by following the docs. I opted for installing it on a separate host (another lxc container) as recommended in the docs. I used the systemd unit file to ensure that the runner comes back online after system reboots. I installed tailscale on this act runner as well, so that it can have the same “networking privileges” as the main instance.
After registering this runner and starting the daemon, it appeared in /admin/actions/runners
:
@@ -283,8 +282,9 @@ jobs: