I am wanting to host a git repository for personal use, does anyone have recommendations between Gitea and Gitlab CE? Other options would also be fine if you have used them.
Gitlab would be a no brainer but appears to be a major pain to set up if I want to access it both from a local IP, and also from a domain name that points to a reverse proxy for it.
I have the gitlab ce docker container running behind a reverse proxy and I haven’t had any issues (other than a weird WebIDE issue, but there was documentation on how to change the config file for it so whatevs).
If you have a domain name set up, why would you want to use a local IP? It would still resolve to the same conatiner?
This isn’t so bad, it runs chef-client to do all of the provisioning. You just need a couple of environment variables.
That being said, for personal use I’d go with that lightweight option. I have no experience with it but GitLab is full featured for managing teams, projects, and automation.
How deep down the rabbit hole do you want to go?
Nope, it will be running on a local machine, and the reverse proxy is on a VPS. This is because the ISP I have at home does not allow running services.
I want to be able to type in the local ip or local hostname of the machine at home and access it, I also want to be able to access it from elsewhere by typing in the subdomain.
I think external_url is the one I want, but AFAIK it only supports only one value.
Yeah, but you can still access it locally. My gitlab is gitlab.admindev.tech or whatever, but I can still go to 172.16.0.159 or whatever. You would just have your domain pointed at your public IP and then have that forward it to the local IP.
DomainName -> PublicIp -> LocalIp
This can be done at the NAT/Port Forwarding router level.
Is yours local service or vps?
Local. It’s running on my KVM host.
I use NameCheap to point my domain to my public IP at my house. From there I go into my router settings and hit up the firewall configuration and create an entry that accepts 443 and forwards it to the IP of the GitLab VM.
This option is so much easier because Linode/Digital Ocean/Lightsail will handle that for you as long as you enter the correct info in the web console.
I am not allowed to do that according to my ISP.
I have a VPS and my domain is pointing to it, I have nextcloud and stuff working, but the specs on it suck so I don’t have a free gb+ of ram on it to allocate for this. I was planning to host it on my local machine, then wireguard to the VPS, then on the VPS a reverse proxy that also adds ssl.
I guess full-featured also mean full ram. 2gb ram at initial start-up for gitlab docker. WTF does it need that much for.
Well, I got Gitea running locally, it is also working fine with the reverse proxy. It is sitting at 112.5mb of ram for the docker container, which isn’t too bad. The next step is figuring out how to setup a ssh reverse proxy or whatever it would be called and have it work with the gitea keys.