Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
Gitlab 13.9
11–20 of 63 posts
Re: Gitlab 13.9
#12Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
I started out using Gitlab for my personal repos, but have switched to using bare Git repos on a VPS for the last few years. If you won't be collaborating with anyone else, nothing beats being able to just write: ssh $HOST git init --bare repo/foo git remote add origin $HOST:repo/foo
Re: Gitlab 13.9
#13Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
As I see it: GitLab has CI and a whole host of other features (artifact repositories, pages, ...) Gittea is a nice WebUI for viewing source files with simple issue and patch management. bare-git is fine if you don't need any web presence.
cgit or gitweb can be nice additions to bare git for simple repository browsing without the full 'project managment' aspects that gitlab/gitea/redmine etc. add
Re: Gitlab 13.9
#14Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
I started out using Gitlab for my personal repos, but have switched to using bare Git repos on a VPS for the last few years. If you won't be collaborating with anyone else, nothing beats being able to just write: ssh $HOST git init --bare repo/foo git remote add origin $HOST:repo/foo
Re: Gitlab 13.9
#15Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
bare repo synced up to S3 is my vote, with end to end encryption enabled. Why give some third party access to your data if you don't need to?
Re: Gitlab 13.9
#16Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
[0] https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-rel...
Re: Gitlab 13.9
#17Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
Another option might be SourceHut, although it's officially still in alpha. https://sourcehut.org/
Re: Gitlab 13.9
#18Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
Another option might be SourceHut, although it's officially still in alpha. https://sourcehut.org/
Re: Gitlab 13.9
#19I've had some pains when creating base job definitions that I had to modify later (one of them is that after_script doesn't fail the job if it fails, for example) and I think I can solve almost all of them with this new feature.
Gitlab is one of the few programs I use where I'm actually looking forward to updates: things rarely break in updates and I have actual, useful improvements every month.
Re: Gitlab 13.9
#20Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.
Do you actually need CI? That's not a trick question; I don't use it on any of my personal projects. If so, GitLab is quite nice.
I absolutely love Gitea. If there's a nonzero chance I might ever want to rope in a friend on a personal project, Gitea makes it super easy to configure their permissions, let them open pull requests, etc.
If I know I'm never going to involve someone else, and I won't need CI, then bare-git repos are brilliant. I use this for things like maintaining a version history of files in /etc on my servers.