diff --git a/.gitmodules b/.gitmodules
new file mode 100644
index 00000000..cbbc36bc
--- /dev/null
+++ b/.gitmodules
@@ -0,0 +1,3 @@
+[submodule "themes/hugo-video"]
+ path = themes/hugo-video
+ url = https://github.com/martignoni/hugo-video.git
diff --git a/config.yaml b/config.yaml
index d7a4bec8..8df132e7 100644
--- a/config.yaml
+++ b/config.yaml
@@ -7,7 +7,9 @@ preserveTaxonomyNames: true
pygmentsstyle: "monokai"
pygmentscodefences: false
pygmentscodefencesguesssyntax: true
-theme: archie
+theme:
+ - archie
+ - hugo-video
title: davegallant
params:
diff --git a/content/post/setting-up-gitea-actions-with-tailscale/gitea-runner.webm b/content/post/setting-up-gitea-actions-with-tailscale/gitea-runner.webm
new file mode 100644
index 00000000..3bd17f91
Binary files /dev/null and b/content/post/setting-up-gitea-actions-with-tailscale/gitea-runner.webm differ
diff --git a/content/post/setting-up-gitea-actions-with-tailscale.md b/content/post/setting-up-gitea-actions-with-tailscale/index.md
similarity index 99%
rename from content/post/setting-up-gitea-actions-with-tailscale.md
rename to content/post/setting-up-gitea-actions-with-tailscale/index.md
index 7bf4760c..c279438e 100644
--- a/content/post/setting-up-gitea-actions-with-tailscale.md
+++ b/content/post/setting-up-gitea-actions-with-tailscale/index.md
@@ -195,6 +195,10 @@ jobs:
--limit ${{ matrix.host }}
```
+And voilà:
+
+{{< video src="gitea-runner" >}}
+
## Conclusion
Gitea Actions are fast and the resource footprint is minimal. My gitea instance is currently using around 250mb of memory and a small fraction of a single cpu core (and the runner is using a similar amount of resources). This is impressive since many alternatives tend to require substantionally more resources (ahem, gitlab). It certainly doesn't hurt that the codebase is largely written in go.
diff --git a/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/gitea-runner.webm b/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/gitea-runner.webm
new file mode 100644
index 00000000..3bd17f91
Binary files /dev/null and b/public/blog/2023/12/10/setting-up-gitea-actions-with-tailscale/gitea-runner.webm differ
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 01a89a7b..a9d48a3c 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
@@ -231,6 +231,11 @@ jobs:
--inventory inventory
--limit ${{ matrix.host }}
+
Gitea Actions are fast and the resource footprint is minimal. My gitea instance is currently using around 250mb of memory and a small fraction of a single cpu core (and the runner is using a similar amount of resources). This is impressive since many alternatives tend to require substantionally more resources (ahem, gitlab). It certainly doesn’t hurt that the codebase is largely written in go.
By combining gitea with the networking marvel that is tailscale, running workflows becomes simple and fun. Whether you are working on a team or working alone, this setup ensures that your workflows are securely accessible from anywhere with an internet connection.