What we removed in 4.0:
SQLite support (I like it but this database got locked
when several users use gitlab at once)
This is a pitty! I am sure there are many small teams where sqlite is totally sufficient.
Have you been able to measure and determine the problems with sqlite more precisely? It would be interesting to see at which point (number of concurrent users) the problems occur. Also it just reads like some data accessing backend is not properly closing connection / file access, so blocking might be just a bug, not a sqlite limitation.
I personally do like having such important infrastructure like bugtrackers as simple as possible, beeing able to setup anytime anywhere with sqlite backend is really a plus in changing environments.
One important solution is to switch from journal mode to WAL mode. Journal mode (the default) makes readers block writers and vice versa. WAL mode makes it so only writers block writers.
I started to try to get things running at work. We use SLES at work, needless to say this has to be the most annoying product to setup ever.
Also the setup instructions have everything prefixed with sudo, why they don't just say sudo su - user and do the rest as that user is beyond me. Half of the setup could just be a few sh scripts.
I'm about halfway through the setup, but this project won't see a lot of adoption given its insane dependency hell and installation tedium.
I found the installation process to be well described and installation went flawless. It seems like a long process but in the end, it's just because every little step from user creation to ruby installation is described in detail.
I'm opinionated on this since I'm running GitLab.com where you can use GitLab as a service.
GitHub has more features than GitLab. GitLab does have all the essentials to work as a team including merge requests and CI integration. Personally I think the GitLab interface is a bit less cluttered.
The main feature I'm missing is forks/pull-requests across repos. It's a nice way to keep strict control over the main repo while allowing others to commit code at their leisure. I must admit that this took me a little by suprise after installing GL.
This might be the push I need to install GitLab for my biz and site deployments, and bringing on contributors... until now, it seemed like too much hassle when I can simply pay $7/mo to use GitHub mini plan.
Github isn't just a list of features. It is also the community, expertise and maintaining uptime and availability, security, etc. I guess for so little money I don't know why I'd ever use this unless I was working at a bank or somewhere that was obsessed with security and self-hosting (and didn't realize github is better at this than they are).
Also, I have to admit it is a bit irritating that this is such a direct rip of github. The only real "feature" they're adding over github is getting everything github innovated without paying github.
There are some projects which legally can't be hosted on third party servers. Sometimes it's not about security but legal bindings. Even though they don't make sense, they do exist. There are also situations where you simply can't explain the benefits of Github to the decision maker.
Isn't this the same argument as saying that linux is a ripoff of unix without compensating the unix creators? Where would we be if we gave in to such notions?
I agree that it bothers me to see Gitlab UI looking too similar to GitHub. I’m hoping that GitHub would not pursue any action against it. I also agree that Gitlab can’t compete against GitHub in the areas you’ve listed.
For my company, however, Gitlab makes a lot of sense. We have a large number of small and close source client projects to manage. We don’t want to pay for file hosting, e.g. $50 a month for 50 repos, when each repo is tiny and we can easily and cheaply host them. GitHub Enterprise is also out of question, as it is not very affordable by a small company.
Cost factor aside, Gitlab does have advantages over GitHub. Legal requirement is one, and the ability to integrate with other tools in the company is also quite nice. Although this feature has not been implemented yet, I look forward to the ability for Gitlab to integrate with Jenkins and display build status.
I will continue to use GitHub for personal and open source projects. For client work, Gitlab will be the one I use.
I wouldn't throw out the phrase "so little money" so eagerly.
I'm a student with practically no income, and I have about 50 repositories for my school and weekend projects. To use GitHub, I would have to pay them $100/mo.
First of all, GitLab is awesome! However, I have to agree on making the installation steps easier. I was running GitLab 3.1 and followed the instructions on the official "From 3.1 to 4.0" update guide but when I checked GitLab's status at the end, there were several errors or uncomplete parts. Considering its a major release, I decided to reinstall everything from scratch instead of trying to manually fix everything displayed on the GitLab status check.
So it now supports both MySQL and Postgres, even though MySQL is preferred. Does anyone know what that means for a Postgres guy like me? Does "MySQL is preferred" mean that it has known bugs on Postgres? Is it usable?
Gitlab uses the idea of a notable to signify things that can be commented on. For git commits comments they store the git commit in the column which you need an explicit cast for in postgres
I think there is one other thing too. But this was when installed version 3 they may have changed this
Yes by default there are 4 different type of privileges per project that can be assigned to a user : guest, reporter, developer, master & owner. The list of what each is allowed to do can be found here : http://demo.gitlabhq.com/help/permissions
I've been looking at options for Git repos inside the firewall so happy to see this. Has anyone used Atlassian Stash too? How does it stack up vs GitLab? I've been using GitStack for a few months, which hasn't been bad for the basics.
[+] [-] BUGHUNTER|13 years ago|reply
Have you been able to measure and determine the problems with sqlite more precisely? It would be interesting to see at which point (number of concurrent users) the problems occur. Also it just reads like some data accessing backend is not properly closing connection / file access, so blocking might be just a bug, not a sqlite limitation.
Did you read http://www.sqlite.org/lockingv3.html ?
I personally do like having such important infrastructure like bugtrackers as simple as possible, beeing able to setup anytime anywhere with sqlite backend is really a plus in changing environments.
[+] [-] beagle3|13 years ago|reply
[+] [-] mememememememe|13 years ago|reply
[deleted]
[+] [-] n0nick|13 years ago|reply
This is feedback I heard from fellow developers as well.
I'm curious as to whether the maintainers are planning to simplify the list of dependencies and installation steps in the upcoming versions.
[+] [-] makmanalp|13 years ago|reply
https://github.com/atomic-penguin/cookbook-gitlab
also this:
https://github.com/gitlabhq/gitlab-vagrant-vm
[+] [-] sytse|13 years ago|reply
I hope to improve our Chef Cookbook for GitLab to the point where it can replace some of the scripts you need now.
Was there any particular part of the installation guide that we can improve in the near future?
(I run GitLab.com, offering GitLab as a service)
[+] [-] mitchty|13 years ago|reply
Also the setup instructions have everything prefixed with sudo, why they don't just say sudo su - user and do the rest as that user is beyond me. Half of the setup could just be a few sh scripts.
I'm about halfway through the setup, but this project won't see a lot of adoption given its insane dependency hell and installation tedium.
[+] [-] Xylakant|13 years ago|reply
[+] [-] rustc|13 years ago|reply
To anyone who is using this, how would you compare 4.0 to the current GitHub, in terms of UI/Features?
I'm thinking of moving from a third party host to GitLab. What should I be aware of?
[+] [-] sytse|13 years ago|reply
GitHub has more features than GitLab. GitLab does have all the essentials to work as a team including merge requests and CI integration. Personally I think the GitLab interface is a bit less cluttered.
A list of things that are still missing from GitLab can be found on http://gitlab.uservoice.com/forums/176466-general
The highest votes items there (namespacing) just got added in GitLab 4.0
And the lead author Dmitriy had added many improvements each months for the last few months. Also the number of good pull requests is steadily increasing https://github.com/gitlabhq/gitlabhq/pulls?direction=desc...
If you want to run your own server you need to understand basic Unix systems operations. If you are comfortable with the installation guide than you should be fine https://github.com/gitlabhq/gitlabhq/blob/master/doc/install...
[+] [-] Xylakant|13 years ago|reply
[+] [-] josscrowcroft|13 years ago|reply
Looks fantastic though congrats.
[+] [-] eagsalazar2|13 years ago|reply
Also, I have to admit it is a bit irritating that this is such a direct rip of github. The only real "feature" they're adding over github is getting everything github innovated without paying github.
[+] [-] egeozcan|13 years ago|reply
[+] [-] InclinedPlane|13 years ago|reply
[+] [-] bchen|13 years ago|reply
For my company, however, Gitlab makes a lot of sense. We have a large number of small and close source client projects to manage. We don’t want to pay for file hosting, e.g. $50 a month for 50 repos, when each repo is tiny and we can easily and cheaply host them. GitHub Enterprise is also out of question, as it is not very affordable by a small company.
Cost factor aside, Gitlab does have advantages over GitHub. Legal requirement is one, and the ability to integrate with other tools in the company is also quite nice. Although this feature has not been implemented yet, I look forward to the ability for Gitlab to integrate with Jenkins and display build status.
I will continue to use GitHub for personal and open source projects. For client work, Gitlab will be the one I use.
[+] [-] Void_|13 years ago|reply
I'm a student with practically no income, and I have about 50 repositories for my school and weekend projects. To use GitHub, I would have to pay them $100/mo.
[+] [-] ufukbay|13 years ago|reply
[+] [-] MartinMond|13 years ago|reply
So it now supports both MySQL and Postgres, even though MySQL is preferred. Does anyone know what that means for a Postgres guy like me? Does "MySQL is preferred" mean that it has known bugs on Postgres? Is it usable?
[+] [-] sytse|13 years ago|reply
Right now all the tests are green on PostgreSQL https://travis-ci.org/gitlabhq/gitlabhq/jobs/3796920
[+] [-] wh-uws|13 years ago|reply
Gitlab uses the idea of a notable to signify things that can be commented on. For git commits comments they store the git commit in the column which you need an explicit cast for in postgres
I think there is one other thing too. But this was when installed version 3 they may have changed this
You can also read more about it on the original support pull request https://github.com/gitlabhq/gitlabhq/pull/1666
[+] [-] mikhailt|13 years ago|reply
An example, CS team have access to issues/wikis only while the dev team have unlimited access.
This is our only deal breaker with GitHub.
If you know of other git-based system/service that does this, please let me know.
Thanks!
[+] [-] caissy|13 years ago|reply
[+] [-] mountaineer|13 years ago|reply
[+] [-] daniellockard|13 years ago|reply
[+] [-] sippndipp|13 years ago|reply