4 ms·
I had a gitlab instance on one of my computers that is online 24/7. It is a good solution, but my system was compromised by exploiting ruby / gitshell . Also it
by drinchev 12y ago
I had a gitlab instance on one of my computers that is online 24/7. It is a good solution, but my system was compromised by exploiting ruby / gitshell . Also it took way too much system resources to operate.
Of course it's my responsibility to patch software I'm using, but after considering how much time I would need to run gitlab on my own host ( incl. server upgrade, security configuration, may be kernel + docker installation, etc. ) I decided to go to a paid repo at GitHub.
- webmaven 12y agoHad you considered GitLab's free hosting?
- drinchev 12y agoI didn't consider hosting from GitLab at all. The thing I considered was that GitLab is an open-source project, so I can modify it the way I want ( I actually contributed a super small patch ( https://github.com/gitlabhq/gitlab-ci-runner/pull/16 https://github.com/gitlabhq/gitlab-ci-runner/pull/16 ) . Anyway free hosting for me for a platform that you can install on your server has always been a no-option, because I want to control the content.
- webmaven 12y agoSo instead you'd rather choose a paid hosting account for a solution where you don't have that self-hosting option?