add cron config to gitea setup

active/podman_gitea/gitea.md

@@ -5,6 +5,7 @@
     - [Create the gitea user](#create-the-gitea-user)
     - [Convert Compose to Quadlet](#convert-compose-to-quadlet)
     - [Install Quadlets](#install-quadlets)
+    - [Editing Configs within Container](#editing-configs-within-container)
   - [Gitea Runners](#gitea-runners)
     - [Firewall Rules](#firewall-rules)
     - [Install](#install)
@@ -67,6 +68,12 @@ systemctl --user daemon-reload
 systemctl --user start gitea postgres
 ```
 
+### Editing Configs within Container
+
+```bash
+apk add vim
+```
+
 ## Gitea Runners
 
 <https://docs.gitea.com/next/usage/actions/act-runner/#install-with-the-docker-image>
@@ -99,6 +106,26 @@ Each org or project with a package registry will have its own cleanup rules. For
 services -> settings -> Packages -> Add Cleanup Rule will allow you to create a cleanup
 rule for packages stored under the "services" org. These cleanup rules should run automatically.
 
+You'll need to enable `cron` and `cron.cleanup_packages` in the app.ini (/data/gitea/conf).
+
+Cron: <https://docs.gitea.com/administration/config-cheat-sheet#cron-cron>
+
+Package Cleanup: <https://docs.gitea.com/1.19/administration/config-cheat-sheet#cron---cleanup-hook_task-table-croncleanup_hook_task_table>
+
+```conf
+[cron]
+ENABLED             = true
+RUN_AT_START        = true
+NOTICE_ON_SUCCESS   = true
+SCHEDULE            = @midnight
+
+[cron.cleanup_packages]
+ENABLED             = true
+RUN_AT_START        = true
+SCHEDULE            = @midnight
+NOTICE_ON_SUCCESS   = true
+```
+
 On the other hand, the docker builder cache will balloon out of control over time. The gitea
 docker runner is handled outside of Gitea's context, so you'll need to clean it up yourself.