diff --git a/config.yaml b/config.yaml index 8df132e7..09d2b5eb 100644 --- a/config.yaml +++ b/config.yaml @@ -25,12 +25,15 @@ params: - css/custom.css social: + - name: Email + icon: at-sign + url: 'mailto:me@davegallant.ca' + - name: LinkTree + icon: compass + url: 'https://linktr.ee/davegallant' - name: GitHub icon: github url: 'https://github.com/davegallant' - - name: Twitter - icon: twitter - url: 'https://twitter.com/davega11ant/' - name: Mastodon icon: speaker url: https://mastodon.social/@davegallant 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 14979fa5..ac891f60 100644 --- a/content/post/setting-up-gitea-actions-with-tailscale/index.md +++ b/content/post/setting-up-gitea-actions-with-tailscale/index.md @@ -134,9 +134,9 @@ http: - 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](https://docs.gitea.com/installation/install-with-docker#ssh-container-passthrough). I decided to keep it simple and not use ssh, since communicating over https is perfectly fine for my use case. +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](https://docs.gitea.com/installation/install-with-docker#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](https://gitea.my-tailnet-name.ts.net) from within your tailnet. +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 @@ -199,6 +199,10 @@ And voilà: {{< video src="gitea-runner" >}} +## Areas for improvement + +One enhancement that I would like to see is the ability to send notifications on workflow failures. Currently, this [doesn't seem possible](https://github.com/go-gitea/gitea/issues/23725). + ## 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 likely helps that the codebase is largely written in go. diff --git a/public/about/index.html b/public/about/index.html index a5c8960a..884463c5 100644 --- a/public/about/index.html +++ b/public/about/index.html @@ -10,7 +10,6 @@ - @@ -112,8 +111,9 @@