diff --git a/content/post/setting-up-gitea-actions-with-tailscale/gitea-runners.png b/content/post/setting-up-gitea-actions-with-tailscale/gitea-runners.png index d733190d..5935cd54 100644 Binary files a/content/post/setting-up-gitea-actions-with-tailscale/gitea-runners.png and b/content/post/setting-up-gitea-actions-with-tailscale/gitea-runners.png differ diff --git a/content/post/setting-up-gitea-actions-with-tailscale/gitea-workflow.png b/content/post/setting-up-gitea-actions-with-tailscale/gitea-workflow.png new file mode 100644 index 00000000..0d799795 Binary files /dev/null and b/content/post/setting-up-gitea-actions-with-tailscale/gitea-workflow.png differ diff --git a/content/post/setting-up-gitea-actions-with-tailscale/gitea-workflow.webm b/content/post/setting-up-gitea-actions-with-tailscale/gitea-workflow.webm deleted file mode 100644 index 6300be6a..00000000 Binary files a/content/post/setting-up-gitea-actions-with-tailscale/gitea-workflow.webm and /dev/null differ diff --git a/content/post/setting-up-gitea-actions-with-tailscale/index.md b/content/post/setting-up-gitea-actions-with-tailscale/index.md index d75c76a1..ed4c3b66 100644 --- a/content/post/setting-up-gitea-actions-with-tailscale/index.md +++ b/content/post/setting-up-gitea-actions-with-tailscale/index.md @@ -116,11 +116,24 @@ Something to consider is whether or not you want to use ssh with git. One method 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](https://gitea.my-tailnet-name.ts.net) from within the tailnet. -## Connecting a Runner +## Theming + +I discovered some nice themes for gitea [here](https://git.sainnhe.dev/sainnhe/gitea-themes) and decided to try out gruvbox. + +I added the theme by cloning [theme-gruvbox-auto.css](https://git.sainnhe.dev/sainnhe/gitea-themes/raw/branch/master/dist/theme-gruvbox-auto.css) into `./data/gitea/public/assets/css`. I then added the following to `environment` in `docker-compose.yml`: + +```yaml +- GITEA__ui__DEFAULT_THEME=gruvbox-auto +- GITEA__ui__THEMES=gruvbox-auto +``` + +After restarting the gitea instance, the default theme was applied. + +## Connecting runners I installed the runner by [following the docs](https://docs.gitea.com/usage/actions/quickstart#set-up-runner). 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 gitea 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`: +After registering this runner and starting the daemon, the runner appeared in `/admin/actions/runners`. I added two other runners to help with parallelization. ![image](gitea-runners.png) @@ -146,7 +159,7 @@ jobs: matrix: host: - changedetection - - homelab + - homer - invidious - jackett - ladder @@ -154,6 +167,7 @@ jobs: - plex - qbittorrent - tailscale-exit-node + - tailscale-subnet-router - uptime-kuma steps: - name: Check out repository code @@ -187,7 +201,7 @@ jobs: And voilĂ : -{{< video poster="gitea-workflow" >}} +![image](gitea-workflow.png) You may be wondering how the gitea runner is allowed to connect to the other hosts using ansible? Well, the nodes are in the same tailnet and have [tailscale ssh](https://tailscale.com/tailscale-ssh) enabled. diff --git a/themes/hugo-theme-gruvbox/layouts/_default/_markup/render-image.html b/themes/hugo-theme-gruvbox/layouts/_default/_markup/render-image.html deleted file mode 100644 index e72c9fd2..00000000 --- a/themes/hugo-theme-gruvbox/layouts/_default/_markup/render-image.html +++ /dev/null @@ -1 +0,0 @@ -{{ partial "image.html" (dict "src" .Destination "alt" .PlainText "caption" .Title "page" .Page "lazy" true) }}