Add systemd units to run actions and homelab

act_runner.service

@@ -0,0 +1,16 @@
+[Unit]
+Description=Gitea Actions runner
+Documentation=https://gitea.com/gitea/act_runner
+After=docker.service
+
+[Service]
+ExecStart=/usr/bin/act_runner daemon --config /home/matthew/homelab/host-runner.yaml
+ExecReload=/bin/kill -s HUP $MAINPID
+WorkingDirectory=/home/matthew/act_runner
+TimeoutSec=0
+RestartSec=10
+Restart=always
+User=matthew
+
+[Install]
+WantedBy=multi-user.target

build-certs.sh

@@ -7,4 +7,5 @@ docker compose run --rm certbot certonly --webroot --webroot-path /var/www/certb
   -d jellyseerr.loadingm.xyz \
   -d servarr.loadingm.xyz \
   -d karakeep.loadingm.xyz \
-  -d ollama.loadingm.xyz
+  -d ollama.loadingm.xyz \
+  -d gpodder.loadingm.xyz

homelab.service

@@ -0,0 +1,20 @@
+[Unit]
+Description=Homelab services
+Requires=docker.service
+After=docker.service
+
+[Service]
+Restart=always
+User=root
+Group=docker
+TimeoutStopSec=15
+WorkingDirectory=/home/matthew/homelab
+# Shutdown container (if running) when unit is started
+ExecStartPre=/usr/bin/docker compose -f docker-compose.yaml down
+# Start container when unit is started
+ExecStart=/usr/bin/docker compose -f docker-compose.yaml up
+# Stop container when unit is stopped
+ExecStop=/usr/bin/docker compose -f docker-compose.yaml down
+
+[Install]
+WantedBy=multi-user.target

nginx/sites-enabled/gpodder

@@ -0,0 +1,70 @@
+##
+# You should look at the following URL's in order to grasp a solid understanding
+# of Nginx configuration files in order to fully unleash the power of Nginx.
+# https://www.nginx.com/resources/wiki/start/
+# https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
+# https://wiki.debian.org/Nginx/DirectoryStructure
+#
+# In most cases, administrators will remove this file from sites-enabled/ and
+# leave it as reference inside of sites-available where it will continue to be
+# updated by the nginx packaging team.
+#
+# This file will automatically load configuration files provided by other
+# applications, such as Drupal or Wordpress. These applications will be made
+# available underneath a path with that package name, such as /drupal8.
+#
+# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
+##
+
+server {
+    listen 80;
+    listen [::]:80;
+    server_name gpodder.loadingm.xyz;
+
+    location /.well-known/acme-challenge/ {
+        root /var/www/certbot;
+    }
+
+    # Uncomment to redirect HTTP to HTTPS
+    location / {
+        return 301 https://$host$request_uri;
+    }
+}
+
+# Default server configuration
+#
+server {
+
+	# SSL configuration
+	listen 443 ssl;
+	listen [::]:443 ssl;
+    http2 on;
+
+	server_name gpodder.loadingm.xyz;
+
+    ssl_certificate /etc/letsencrypt/live/loadingm.xyz/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/loadingm.xyz/privkey.pem;
+    # include /etc/letsencrypt/options-ssl-nginx.conf;
+    # ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
+    ssl_trusted_certificate /etc/letsencrypt/live/loadingm.xyz/chain.pem;
+
+	root /data/site;
+
+	location /hosted {
+		index index.html; 
+		autoindex on;
+	}
+
+	location / {
+		# First attempt to serve request as file, then
+		# as directory, then fall back to displaying a 404.
+		try_files $uri $uri/ =404;
+	}
+
+	# deny access to .htaccess files, if Apache's document root
+	# concurs with nginx's one
+	#
+	#location ~ /\.ht {
+	#	deny all;
+	#}
+}