shockrah/infra
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
702cc02edd
infra/infra/gitea-instance
History
shockrah f0e815e9cb Ignoring sensitive tfvars file
2023-11-28 21:21:55 -08:00
..
.gitignore Ignoring sensitive tfvars file 2023-11-28 21:21:55 -08:00
backend.tf Basic skeleton for new gitea server ( not provisioned yet ) 2023-11-27 22:28:06 -08:00
firewall.tf Basic skeleton for new gitea server ( not provisioned yet ) 2023-11-27 22:28:06 -08:00
host.tf Basic skeleton for new gitea server ( not provisioned yet ) 2023-11-27 22:28:06 -08:00
readme.md Simple docs for future git server 2023-11-27 17:53:31 -08:00
route53-gitea-project-athens-xyz.tf Basic skeleton for new gitea server ( not provisioned yet ) 2023-11-27 22:28:06 -08:00
ssh.tf Basic skeleton for new gitea server ( not provisioned yet ) 2023-11-27 22:28:06 -08:00
variables.tf Basic skeleton for new gitea server ( not provisioned yet ) 2023-11-27 22:28:06 -08:00

readme.md

Gary Gitea

This folder contains all the infra code for setting up the Gitea instance. This will be a single public server that contains both the main Gitea service as well as the CI/CD pipeline that we'll be using for deployment things. This is all part of a move away from hosted services such as Gitlab.

Services To Support

  • Gitea Git services
  • LFS for ( Temper ) related projects that require larger file storage

Why the move to self hosted Gitea

Dubious copyright protection/user agreements with SaaS providers. I would much rather setup my own repositories with all content in one place that I can manage on my own instead.

Why Vultr

Two reasons:

  • To not rope myself further into using only AWS.

  • Good Terraform support which makes the infrastructure setup relatively painless