41–50 of 54 posts
I'm considering GitLab for use at work. How does it stack up against Atlassian Stash? ( https://www.atlassian.com/software/stash/overview )
One of the reasons that we chose Gitlab is because it's open source. We've made some tweaks to it so that it better fits our needs.
2 biggest downsides to GitLab: 1) It's a resource hog. Big time. 2) It's incredibly hard to set up. The installation instructions and the development instructions are essentially the same. Key point, an end user should never have to `bundle install`, ever .
Agreed on both counts - I blame Ruby. We enjoy using it, but to new users I would recommend looking into gitbucket https://github.com/takezoe/gitbucket written in scala and no install necessary!
2 biggest downsides to GitLab: 1) It's a resource hog. Big time. 2) It's incredibly hard to set up. The installation instructions and the development instructions are essentially the same. Key point, an end user should never have to `bundle install`, ever .
@2) Maybe in an older version, but not anymore. The installation is not as nice as in a single apt-get call, but the install documentation makes a setup a matter of copy'n'paste.
Earlier quoted context omitted.
I've had to compare the two. At the current state, Stash is better than GitLab in almost all ways. Better UI, more features and other small things that make a big difference (e.g. repo sync). GitLab, on the other hand, has two advantages over Stash. Firstly it's open source (+free). Secondly and most importantly, GitLab is under active development and there is a new release with reasonable amount of content every mon…
At the current state, Stash is better than GitLab Yes. GitLab, on the other hand, has two advantages over Stash ... GitLab is under active development and there is a new release with reasonable amount of content every month. No. Stash 2.9 was just released [1] about seven weeks after Stash 2.8 [2] about seven weeks after Stash 2.7 [3]. [1] https://confluence.atlassian.com/display/STASH/Stash+2.9+rel... [2] https://co…
2 biggest downsides to GitLab: 1) It's a resource hog. Big time. 2) It's incredibly hard to set up. The installation instructions and the development instructions are essentially the same. Key point, an end user should never have to `bundle install`, ever .
@2) Maybe in an older version, but not anymore. The installation is not as nice as in a single apt-get call, but the install documentation makes a setup a matter of copy'n'paste.
(Late) Edit: any problems I've ever had with upgrades have been related to not properly adjusting settings when moving new config files around. For example, in upgrading to 6.3 I failed to copy over my custom listen lines in unicorn for a non-standard port.
2 biggest downsides to GitLab: 1) It's a resource hog. Big time. 2) It's incredibly hard to set up. The installation instructions and the development instructions are essentially the same. Key point, an end user should never have to `bundle install`, ever .
Agreed on both counts - I blame Ruby. We enjoy using it, but to new users I would recommend looking into gitbucket https://github.com/takezoe/gitbucket written in scala and no install necessary!
Earlier quoted context omitted.
At the current state, Stash is better than GitLab Yes. GitLab, on the other hand, has two advantages over Stash ... GitLab is under active development and there is a new release with reasonable amount of content every month. No. Stash 2.9 was just released [1] about seven weeks after Stash 2.8 [2] about seven weeks after Stash 2.7 [3]. [1] https://confluence.atlassian.com/display/STASH/Stash+2.9+rel... [2] https://co…
Stash isn't open source, though.
2 biggest downsides to GitLab: 1) It's a resource hog. Big time. 2) It's incredibly hard to set up. The installation instructions and the development instructions are essentially the same. Key point, an end user should never have to `bundle install`, ever .
I maintain a set of Chef cookbooks (more Ruby, I'm afraid ;)) that includes a cookbook for GitLab[1]. The cookbook may not be the best, but it has been serving us well. There are numerous other Chef cookbooks for GitLab. IMHO GitLab is easy to set up compared to something like Postfix. Making a GitLab server do what it's supposed to do is straightforward. You just follow all the steps. Making Postfix work as a proper…
Heh, I feel exactly the opposite.
2 biggest downsides to GitLab: 1) It's a resource hog. Big time. 2) It's incredibly hard to set up. The installation instructions and the development instructions are essentially the same. Key point, an end user should never have to `bundle install`, ever .
You might try RhodeCode, we spend a lot of resources recently into an Installer for it that makes a few clicks installation, even for windows.