From: Shane Jaroch <chown_tee@proton.me>
Date: Sat, 24 Jan 2026 02:28:00 +0000 (-0500)
Subject: gitea update to use git not gg
X-Git-Url: https://git.nutra.tk/v2?a=commitdiff_plain;h=55b74c1c8d93ffb100388b04cbcdb76d2edf7ba1;p=nutratech%2Fvps-root.git

gitea update to use git not gg
---

diff --git a/docs/gitea.md b/docs/gitea.md
index 1755f05..a690601 100644
--- a/docs/gitea.md
+++ b/docs/gitea.md
@@ -23,14 +23,8 @@ HOST="my-gitea.server" SSH_USER="admin" ~/.backups/pg_backups/gitea-backup.sh
 
 **Prerequisites (Sudo Access):**
 
-Since the script runs non-interactively, your SSH user must be able to run `gitea` commands as the Gitea user without a password.
+The script attempts to use `sudo`. Because it uses `ssh -t`, you can enter your sudo password interactively.
 
-On the **Gitea Server**, add this to `/etc/sudoers` (using `sudo visudo`):
-
-```text
-# Allow shane to run commands as gg without a password
-shane ALL=(gg) NOPASSWD: /usr/local/bin/gitea
-```
 
 **What it does:**
 
@@ -74,7 +68,7 @@ If your backups are large (e.g., hundreds of MBs), it's likely due to **repo-arc
 
 ```bash
 # On the server
-sudo -u gg rm -rf /var/lib/gitea/data/repo-archive/*
+sudo -u git rm -rf /var/lib/gitea/data/repo-archive/*
 ```
 
 ## Update Procedure
diff --git a/etc/gitea/app.ini b/etc/gitea/app.ini
index b74b274..47d7c7b 100644
Binary files a/etc/gitea/app.ini and b/etc/gitea/app.ini differ
diff --git a/etc/systemd/system/gitea.service b/etc/systemd/system/gitea.service
new file mode 100644
index 0000000..0a03668
Binary files /dev/null and b/etc/systemd/system/gitea.service differ
diff --git a/etc/systemd/system/klaus.service b/etc/systemd/system/klaus.service
index e608798..8bcb599 100644
Binary files a/etc/systemd/system/klaus.service and b/etc/systemd/system/klaus.service differ
diff --git a/scripts/manage_repos.py b/scripts/manage_repos.py
index 56471d6..a634b25 100755
--- a/scripts/manage_repos.py
+++ b/scripts/manage_repos.py
@@ -169,7 +169,7 @@ def cmd_init(args, remote):
     # Safe Directory
     # We need to run this globally or on the system level, but running it locally for the user often works
     # if the user accessing it is the one running this.
-    # However, 'git config --global' on remote affects the remote user (gg).
+    # However, 'git config --global' on remote affects the remote user (git).
     remote_run(
         remote, ["git", "config", "--global", "--add", "safe.directory", full_path]
     )