4 ms·

GitHub offers on-prem as well. Of course it's not open source and not potentially free like GitLab https://enterprise.github.com/features https://enterprise.git

by jshmrsn 10y ago

GitHub offers on-prem as well. Of course it's not open source and not potentially free like GitLab https://enterprise.github.com/features https://enterprise.github.com/features

Normal_gaussian 10y ago
$250/user/year, blocks of 10, min 10 Ouch. If you run your own servers already it's financially worth hosting your own gitlab at the minimum price point. I expect it will be the big orgs who don't move due to integration costs.
- was_boring 10y ago
  Let's be honest, does anyone pay full price beyond 10 users? If there's anything I've learned it's that the word "enterprise" means "negotiable." I suspect they put that out there so they have a place to start without the costly interaction of emails coming in saying "how much for x people."
  - Normal_gaussian 10y ago
    When their very first price point leaves it cheaper for me to do in house I'm not wasting time negotiating.
tracker1 10y ago
I like Github's UI slightly better (though it's been about a year since I've tried Gitlab)... the recent db issue has me concerned though. That said, I think it's always worth considering using a tool because of their options for the open-source community... github, travis-ci etc have changed the way a lot of people work. GitLab might be what I reach for for self-hosting, but more likely to try the community/open edition first. Using VSO (VisualStudio.com) for hosting at work, and some of the integration parts are very nice... Though no idea what a private TFS instance costs.
- Ellahn 10y ago
  I use Gitlab and the DB issue only affected me in regards to CI, and I believe this is true to anyone that was affected at all. They did a manual Backup before meddling with stuff so they only lost data from a really small timeframe. CI downtime, on the other hand, is troublesome. I love using Gitlab CI and it didn't take me more than a few minutes to manually deploy what I had to, but I decided I need most of my CI to be controlled by me. The end result is a simple refactor of my test and deploy specs to their own rake tasks (Could be Bash scriots or whatever) and I'll have Gitlab run a simple gle command, if it goes down I run the command manually... Now some eventual downtime is not such a deal breaker anymore, and I continue having private repos and CI (Awesome CI) for even the smallest (And private) projects I work on... Not a bad deal if I do say so myself.

by jshmrsn 10y ago

GitHub offers on-prem as well. Of course it's not open source and not potentially free like GitLab https://enterprise.github.com/features https://enterprise.github.com/features

Normal_gaussian 10y ago

$250/user/year, blocks of 10, min 10 Ouch. If you run your own servers already it's financially worth hosting your own gitlab at the minimum price point. I expect it will be the big orgs who don't move due to integration costs.

was_boring 10y ago
Let's be honest, does anyone pay full price beyond 10 users? If there's anything I've learned it's that the word "enterprise" means "negotiable." I suspect they put that out there so they have a place to start without the costly interaction of emails coming in saying "how much for x people."
- Normal_gaussian 10y ago
  When their very first price point leaves it cheaper for me to do in house I'm not wasting time negotiating.

tracker1 10y ago

I like Github's UI slightly better (though it's been about a year since I've tried Gitlab)... the recent db issue has me concerned though. That said, I think it's always worth considering using a tool because of their options for the open-source community... github, travis-ci etc have changed the way a lot of people work. GitLab might be what I reach for for self-hosting, but more likely to try the community/open edition first. Using VSO (VisualStudio.com) for hosting at work, and some of the integration parts are very nice... Though no idea what a private TFS instance costs.

Ellahn 10y ago
I use Gitlab and the DB issue only affected me in regards to CI, and I believe this is true to anyone that was affected at all. They did a manual Backup before meddling with stuff so they only lost data from a really small timeframe. CI downtime, on the other hand, is troublesome. I love using Gitlab CI and it didn't take me more than a few minutes to manually deploy what I had to, but I decided I need most of my CI to be controlled by me. The end result is a simple refactor of my test and deploy specs to their own rake tasks (Could be Bash scriots or whatever) and I'll have Gitlab run a simple gle command, if it goes down I run the command manually... Now some eventual downtime is not such a deal breaker anymore, and I continue having private repos and CI (Awesome CI) for even the smallest (And private) projects I work on... Not a bad deal if I do say so myself.