5 ms·

I've installed Gitlab in the earlier days, and that seems a lot easer than this guide. Gitlab comes with the web view included.

by monksy 7y ago

folkhack 7y ago
Yeah - as someone who's ran their own git server back in the day with gitolite... 100% agree that GitLab is an easier/quicker solution. Also it's fully featured and WAY simpler to setup on your run-of-the-mill VPS. Personally I have mine hosted at Linode at $25/mo with backups enabled + a $10/mo worker for simple Docker-based builds. This keeps all of my git repos private and 100% in my ownership which is how I prefer to work (sorry GitHub). GitLab is amazing and I'm a huge advocate.
cuspycode 7y ago
I agree with that. I did investigate a number of self-hosted alternatives to Github, but Gitlab was so much easier than any of them. My only complaint about Gitlab is that it uses a lot of CPU even when completely idle. But I was able to fix that easily by throttling it via the "cpulimit" utility. My Fossil server on the other hand, has had no problems at all. Unless your project requires Git, you could save some pain by considering Fossil instead of Git.
mbreese 7y ago
I tried to install Gitlab a few years ago (many), and the installation was such a mess that I eventually just had to give up. Now with docker deployments, things are significantly easier. The method in the post is pretty lightweight for getting a shared git server up and running without Docker. Most of the guide are extra tweaks for web-based comforts like converting README.md’s to HTML, etc. All that said — I use a docker based install of Gitea for this. It doesn’t have as many features as Gitlab, but for an on-site option, it is pretty good. And I find the simplicity of it to be a feature.
jancsika 7y ago
If you run your own instance of Gitlab be sure to require login to view user profile pages. Otherwise you get spam users which will show up in Google results for the domain where you host your Gitlab instance. You'll still get spam users but they won't show up in search. In fact, you could probably set up a honey pot with user profile left publicly accessible. Then when the spammers show up, search Google for the email addys they use. Up should pop all the open source Gitlab instances which don't require a login to view user profiles. :)

I've installed Gitlab in the earlier days, and that seems a lot easer than this guide. Gitlab comes with the web view included.

by monksy 7y ago

I've installed Gitlab in the earlier days, and that seems a lot easer than this guide. Gitlab comes with the web view included.

folkhack 7y ago

Yeah - as someone who's ran their own git server back in the day with gitolite... 100% agree that GitLab is an easier/quicker solution. Also it's fully featured and WAY simpler to setup on your run-of-the-mill VPS. Personally I have mine hosted at Linode at $25/mo with backups enabled + a $10/mo worker for simple Docker-based builds. This keeps all of my git repos private and 100% in my ownership which is how I prefer to work (sorry GitHub). GitLab is amazing and I'm a huge advocate.

cuspycode 7y ago

I agree with that. I did investigate a number of self-hosted alternatives to Github, but Gitlab was so much easier than any of them. My only complaint about Gitlab is that it uses a lot of CPU even when completely idle. But I was able to fix that easily by throttling it via the "cpulimit" utility. My Fossil server on the other hand, has had no problems at all. Unless your project requires Git, you could save some pain by considering Fossil instead of Git.

mbreese 7y ago

I tried to install Gitlab a few years ago (many), and the installation was such a mess that I eventually just had to give up. Now with docker deployments, things are significantly easier. The method in the post is pretty lightweight for getting a shared git server up and running without Docker. Most of the guide are extra tweaks for web-based comforts like converting README.md’s to HTML, etc. All that said — I use a docker based install of Gitea for this. It doesn’t have as many features as Gitlab, but for an on-site option, it is pretty good. And I find the simplicity of it to be a feature.

jancsika 7y ago

If you run your own instance of Gitlab be sure to require login to view user profile pages. Otherwise you get spam users which will show up in Google results for the domain where you host your Gitlab instance. You'll still get spam users but they won't show up in search. In fact, you could probably set up a honey pot with user profile left publicly accessible. Then when the spammers show up, search Google for the email addys they use. Up should pop all the open source Gitlab instances which don't require a login to view user profiles. :)