dave/site
1
0
Fork 0
mirror of https://github.com/davegallant/davegallant.github.io.git synced 2025-08-07 00:58:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 2475d2d67e

Browse Source
This commit is contained in:
davegallant
2024-04-07 22:55:26 +00:00
parent 640438b7ca
commit f89bf22ab5
73 changed files with 76 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
js/flexsearch.f0d4bc1a79b571ac3e13b8791d8f1a53a18dacf82119ae9041a3b79ea360be5304d33d2edcb456764ae7fa6e0555f027c17e0bbacb605ca257e24dd26b9113f1.js → js/flexsearch.4de30be52a726256f045e2f3dbef1aaba4ad9ddcf2657f4190473a382e19b36f313e897dc449218cfc473ec8d80473081225e009985d9f1a81de6c46b844f9d4.js
View File

@@ -21,8 +21,8 @@ version: "3.7" services: gitea: image: gitea/gitea:1.21.1 container_name
config/gitea.json:
{ "TCP": { "443": { "HTTPS": true } }, "Web": { "\${TS_CERT_DOMAIN}:443": { "Handlers": { "/": { "Proxy": "http://127.0.0.1:3000" } } }, }, "AllowFunnel": { "\${TS_CERT_DOMAIN}:443": false } } 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.
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.
Theming# I discovered some themes for gitea here and decided to try out gruvbox.
I added the theme by cloning theme-gruvbox-auto.css into ./data/gitea/public/assets/css. I then added the following to environment in docker-compose.yml:
Theming# I discovered some themes for gitea here.
I added the theme by copying theme-palenight.css into ./data/gitea/public/assets/css. I then added the following to environment in docker-compose.yml:
- GITEA__ui__DEFAULT_THEME=palenight - GITEA__ui__THEMES=palenight After restarting the gitea instance, the default theme was applied.
Connecting runners# I installed the runner by following the docs. I opted for installing it on a separate host 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 the gitea runner as well, so that it can be part of the same tailnet as the main instance.
After registering this runner and starting the daemon, the runner appeared in /admin/actions/runners. I added two other runners to help with parallelization.