fsfe-system-hackers
/
git-server
15
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Ansible playbook for Gitea server (database, gitea, webserver, ldap) https://git.fsfe.org
49 Commits 1 Branch 0 Tags 239 KiB
Jinja 74.7%
Shell 24%
CSS 1.3%
Go to file
tobiasd 609ca87f9d
continuous-integration/drone/push Build was killed Details
mail sending config 		2024-02-22 08:31:56 +01:00
group_vars mail sending config 2024-02-22 08:31:56 +01:00
inventory@0793fc7957 bump inventory 2021-08-05 13:43:04 +02:00
roles mail sending config 2024-02-22 08:31:56 +01:00
.drone.yml adding drone CI for docs sync 2023-01-13 15:20:10 +01:00
.gitignore slightly improve vault/gpg process 2024-02-21 16:30:14 +01:00
.gitmodules add our inventory 2021-04-21 12:32:18 +02:00
README.md added docs.fsfe.org badge to the README 2023-01-13 15:21:59 +01:00
ansible.cfg basic ansible setup 2021-04-21 12:32:45 +02:00
playbook.yml add firewall setup 2022-03-14 16:40:15 +01:00
vaultpw.gpg add tobiasd's GPG key to the vaultpw.gpg file 2024-02-21 16:32:22 +01:00
vaultpw.sh slightly improve vault/gpg process 2024-02-21 16:30:14 +01:00

README.md

FSFE Git Service

in docs.fsfe.org

This Ansible playbook takes care of setting up the FSFE's Git Service, currently based on Gitea. Some sensible bits are encrypted.

  • Base setup of host
  • MySQL database for gitea
  • Gitea configuration
  • Webserver (nginx) including some rate limits

Prerequisites

The machine should be connected via innernet in order to authenticate users via LDAP. This is not part of this playbook.

Updates and configuration

Use this playbook to update the configuration of all elements described above. There is one exception though:

Upgrading Gitea

First, make a snapshot of davy in Proxmox and schedule downtime in the monitoring system. Before proceeding with the update, also announce the possible downtime in the team chat.

To upgrade Gitea itself (in binary form), use /root/bin/gitea-upgrade.sh while providing the desired version. For example:

/root/bin/gitea-upgrade.sh 1.13.7

This takes care of downloading the binary, checking the hashsum, replacing the binary, and reminding you of restarting the service.

Afterwards - especially after major upgrades – compare the upstream templates for this release (choose the tag!) with the ones stored in roles/gitea/files/custom/templates. If substantial changes happened with this release, take the new versions and migrate the custom changes to them. You have to rerun the playbook (ansible-playbook playbook -t gitea) and restart gitea to put these into effect.