Forgejo
Forgejo: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/apps/forgejo. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
Forgejo hosts Git repositories. Follow its Docker installation for one selected release, choosing the documented SQLite or PostgreSQL option deliberately. Start with HTTPS-based Git access; exposing an SSH service is a separate decision and is unnecessary for the first repository test.
Settings and data
Persist the Forgejo data directory and, if used, its separate database. Set the application's root URL to your chosen browser address. Disable open registration if this is a private service. Keep SSH host keys and repository data in the recovery plan; recreating the container must not silently replace them.
Check it
Create a private test repository in the UI, clone it on your own computer, commit a harmless text file, and push it back. Restart and clone into a second directory. This checks actual Git operations, not merely the sign-in page.
When something fails
If clone URLs point to the wrong host, correct the root URL and proxy setup. Authentication errors require checking the chosen Git credential method. Do not put tokens in clone URLs or public command histories. Back up repositories, database, attachments, configuration, and required keys consistently.