Used to host gitlab on my Synology. But it's so resource heavy I stopped. Also the migrations between versions weren't always pain free and costed me many hours of my time.
I'm looking at alternatives.
Poll: Self Hosting Git Repositories
61–70 of 86 posts
Re: Poll: Self Hosting Git Repositories
#62I just host on my VPS and use ssh to access. My VPS gets imaged nightly (for one kind of backup) and versioned back ups using Restic.
I only collaborate with folks who I trust enough to give accounts, which means most are just personal repos.
Re: Poll: Self Hosting Git Repositories
#63Used to host gitlab on my Synology. But it's so resource heavy I stopped. Also the migrations between versions weren't always pain free and costed me many hours of my time. I'm looking at alternatives.
If you don’t need code reviews just… SSH into your server? This is what I do with my Synology, works great.
Re: Poll: Self Hosting Git Repositories
#64You may also want to include onedev [1][2] in your exploration ( https://code.onedev.io/ ) if you also need good CI/CD integration. My experience (as a user) has been pretty good, though I was not involved in the adminstration/setup related aspects but I have been told it doesn't require a lot of maintenance effort. [1] https://github.com/theonedev/onedev [2] https://code.onedev.io/
Can't believe this is not better known. I had huge problems with a git-lfs setup being slow on gitea, but I tried out onedev and its implementation was a magnitude faster. Plus configuring and launching the thing was pretty simple.... easy win!
Re: Poll: Self Hosting Git Repositories
#65if it's for personal use and no access rights are needed, just use ssh. If you need to add more people, but don't require access right for the git repos (i.e. everyone will be able to force push). Still use ssh, but create a git user and git-shell as the shell to improve security. If you want to go one step up, I was looking at soft-serve, however it's too immature yet. So I added a git-shell-commands folder and adde…
Do you mean use VSCode with Remote-SSH and just work on a server?
What you are talking about is remotely accessing and working on a codebase. That has nothing to do with repository management.
As mprime1 replied, it's more on the lines of firing up the terminal to create the git repository. Then go back to your local system and git clone/pull the thing. Then you fire up your local VSCode and work on it and then finally push the changes. This way the whole team can work seamlessly and implement CI/CD while addressing conflicts in real time.
What you are talking about is a beautiful way to work on a remote machine (especially the headless ones) but only when you are the single dev. For a team, you gotta go the other way.
Re: Poll: Self Hosting Git Repositories
#66I wonder whether people monitor resources consumed by processes… A couple of years ago I had installed Gitea, but it was constantly using between 5-10% CPU. I switched to Gogs, and it doesn’t waste CPU cycles. So, I have stayed with Gogs. My needs are minimal (self-hosting for personal use), so I could probably switch to something even more minimal, but so far Gogs works fine.
Re: Poll: Self Hosting Git Repositories
#67Voted others. Just ssh into a Linux server. Have a special user account ‘git’ on the server to hold all the repos so they can just reside at the base directory of its home.
Access via ssh://git@server:~/myproj1.git.
Re: Poll: Self Hosting Git Repositories
#68Gitea (originally a fork of Gogs) is moving fast, and they are adding ActivityPub federation support to the software. This will allow you to collaborate with projects hosted on remote Gitea instances (and other software once they add federation support too). If you are working on FOSS then Codeberg [1] is a good Gitea instance, which offer Woodpecker CI and Codeberg Pages. [1] https://codeberg.org
I believe the Gitea people are also about to add an artifact registry feature. I run a Gitea instance on my Synology to act as a source for flux2 on the living room Kubernetes cluster. I don't want to have that on Github so it'll all work without internet connectivity (still a WIP though). I had my own Gitlab for a long time but at some point its hunger for resources made it uneconomic for my use case. Gitea does les…
I've been using gitea for a while now and still recommend it, I just wish they didn't go the gitlab route and started doing everything and the kitchen sink. They would be better off if they just focused on the federation part and let everything else outside of hosting to other specialized tools.
Re: Poll: Self Hosting Git Repositories
#69Gitea+drone [0] for all my projects for several years : dockerized for even more simplicity. An update is nearly just 'compose pull && compose up'.
Re: Poll: Self Hosting Git Repositories
#70Earlier quoted context omitted.
Do you mean use VSCode with Remote-SSH and just work on a server?
What you are talking about is remotely accessing and working on a codebase. That has nothing to do with repository management. As mprime1 replied, it's more on the lines of firing up the terminal to create the git repository. Then go back to your local system and git clone/pull the thing. Then you fire up your local VSCode and work on it and then finally push the changes. This way the whole team can work seamlessly a…
Why would this not work for a small team?