jr/olomana
1
0
Fork 0
mirror of https://github.com/runyanjake/olomana.git synced 2025-10-04 13:27:28 -07:00
Code Issues Packages Projects Releases Wiki Activity
olomana/gitea/README.md

1.6 KiB
Raw Blame History

Gitea

Self hosted Git

Followed instructions on Gitea page: https://docs.gitea.com/next/installation/install-with-docker

Steps

  1. Create a new user to own the gitea folder.

sudo groupadd gitea && sudo useradd giteauser && sudo usermod -a -G gitea giteauser && chown -r gitea:giteauser .

  1. Run via Docker Compose

docker-compose up -d

  1. Test postgresql

docker exec -it gitea_database bash

psql -h 127.0.0.1 -p 5432 -U gitea

  1. Stop server and set value in app.ini.

Add magic line to /data/persistent/gitea/gitea/gitea/conf/app.ini because local workers will otherwise assume they can use our custom port 3300 to reach services locally. Have to specify local url here.

This goes in the [server] section. (https://docs.gitea.com/next/administration/config-cheat-sheet)

LOCAL_ROOT_URL = http://localhost:3000/

Also modify the following:

ROOT_URL = https://git.whitney.rip

SSH_DOMAIN = git.whitney.rip

Then start containers again.

  1. Go to xxx.xxx.xx.xxx:3300 and fill out initial config. Everything should match up to default values.

Some things that were weird:

  • could not use any port that wasnt default postgresql (5432)

  • had to make sure to specify database container by the right name. Removed custom name and used just "database".

  1. Enable SSH on the server

  • install openssh-server

  • follow https://wiki.archlinux.org/title/Gitea#Enable_SSH_Support

Should be able to clone via HTTPS at this point.

  1. Handle user authentication like you'd do on Github by generating new ssh keys and adding them to the SSH Keys section.

Settings > SSH/GPG Keys > Manage SSH Keys

Now should also be able to clone with SSH.