deploy: 9af473895b174554f25d148115bf7c9ff0ded95c

This commit is contained in:
davegallant
2024-01-07 16:00:09 +00:00
parent 98110de4d9
commit 707a428f92
74 changed files with 75 additions and 75 deletions

View File

@@ -17,7 +17,7 @@ Theming# I discovered some nice themes for gitea here and decided to try out gru
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:
- 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. 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, the runner appeared in /admin/actions/runners. I added three other runners to help with parallelization.
After registering this runner and starting the daemon, the runner appeared in /admin/actions/runners. I added two other runners to help with parallelization.
Running a workflow# Now it’s time start running some automation. I used the demo workflow as a starting point to verify that the runner is executing workflows.
After this, I wanted to make sure that some of my existing workflows could be migrated over.
The following workflow uses a matrix to run a job for several of my hosts using ansible playbooks that will do various tasks such as patching os updates and updating container images.