amy
/
gitea-docker
1
0
Bifurcation 0
Code Tickets 0 Demandes d'ajout 0 Versions 0 Activité
The repo I use to run gitea and caddy all in docker
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
31 Révisions
1 Branche
46 KiB
 
Branche: main
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'main'
${ noResults }
 ZIP  TAR.GZ
Amelia A 7b69fc32b5
Switch to the new major tag 		il y a 1 an
backups Add the backups folder il y a 2 ans
.gitignore Remove the old data folder il y a 2 ans
README.md Remove caddy docker, I'm running elsewhere il y a 2 ans
backup backups now require the git user il y a 2 ans
backup_prune Add checking if we have enough backups il y a 2 ans
docker-compose.yml Switch to the new major tag il y a 1 an

README.md

Gitea in Gitea

This is how I run gitea.

I do it this way because I prioritize;

  • simplicity
  • minimal maintence
  • portability

Usage

Startup

  1. Install docker
  2. Run with docker-compose up -d --build
  3. Optionally put a webserver in front for ssl, I use caddy

Maintence

Upgrade gitea by changing the version in the docker-compose.yml and running docker-compose pull && docker-compose up -d

Data safety

You can do whatever preferred method to back up the contents of docker volumes to back up the gitea-data folder.

However gitea has their own backup & restore method you should consiter. I have created a backup script to create backups and drop them in the ./backups folder. I use this to run from cron.