All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Gitlab 6.0 released
Again another project I love and use very much on a daily basis. First the release notes, then my low end usage tips.
First and foremost are the improved groups.
From now on a group is not just a directory for projects. It also allows you to add users. After user is added to group – it automatically get access to all existing and new projects inside group. You can also have have multiple owners for a group who can manage members/projects. With this GitLab becomes more group oriented. That is why we no longer support global namespaces. Project can be part of group or user only.
Merge requests are now possible between a fork and the original project.
Another nice improvement comes from contributor Izaak Alpert. It allows you to use different workflow depending on your needs.
Still we have more things to present.
Now you can create or remove both git branches and tags with the GitLab UI.
It gives you ability to work with the web ui only. For example to create branch, fix something with the web editor and submit a Merge Request.
Also we polished our UI and made a lot of bug fixes.
Under the hood we refactored a lot of stuff and improved the performance. And one last piece of good news. The upgrade to 6.0 is not so complicated as it used to be for major versions. The only big change is that all projects must be part of a group or user. A bit of preparations, few commands – and you are running GitLab 6.
Links
For full list see CHANGELOG
For new setup follow Setup Guide
For update instructions see Update Guide
Low End Usage
My gitlab VPS has the following specs:
- Debian 7
- 384 MB RAM
- 15 GB Disk
- 1 core (Atom N270)
- Proxmox Hypervisor
I've tried 256 MB RAM, but then the Linux OOM killer came along and nuked Ruby. With the latest release of 6.0, I had to increase the Unicorn Timeout, also because of a memory error, see this link: https://github.com/gitlabhq/gitlabhq/issues/1527#issuecomment-23147741 - But hey, the minimum amount of RAM required according to them is 1 GB. This instance is used by about 20 people daily, and has around 50 projects in it. Performance is more than acceptable with the default nginx settings.
Anybody else running gitlab? Experiences?
Comments
I like GitLab as well but haven't managed to get the memory down too much. It's on a 512MB machine now and it runs just fine. I'll upgrade to 6.0 soon, see if that changes anything.
Same for me eating almost 400mb, only me as user. but sometimes shoots upto 500mb
looks pwerty.
I haven't played with it myself, usually using BitBuckets free private repo's although this looks promising. The memory doesnt really bother me but does anyone know if it works well on openvz (or is this another Zimbra?). I remember trying to install it on a container years ago and it didn't work right.
Mine using OVZ
Looks awesome. Going to install it on one of my idle vps'.
I run GitLab 5.4 on a 512 MB RAM + 512 MB vSwap OpenVZ VPS. The default installation using Puma as a webserver ate too much RAM so I ended up using Nginx + Passenger module. It currently consumes 380 MB of memory when idle: MySQL 100 MB, Passenger+GitLab 150 MB, sidekiq 110 MB and the rest of the system (nginx, redis etc.) ~20 MB. It claims another 10 to 60 MB during normal usage (= one person online). The overall performance is excellent with pages being rendered under 50 ms most of the time.
I was thinking about optimizing MySQL a little but as of now the system runs fine so there's no real need to do that. However, I've tried installing GitLab to MyISAM tables instead of InnoDB and it failed because of an issue with key length.
Oh, awesome! Can I add files directly with the web interface now or do I have to clone the repo, create it manually, and add it back in?
I have a 5.2 instance running on a 768MB OVZ on FlipHost - I don't fancy updating sequentially to six, so I'm just going to back up my repos/snippets and wipe+reinstall to 6.0. GitLab has been great for things like backing up and versioning my config files and whatnot.
I dont see an option to add a new file. You can edit existing ones though.
Running a default install on my 512 MB VPS, with nginx, it leaves just 30MB free. That's a bit too close for comfort. I should probably optimize.
@Rallias @joelgm Correct, for now you can only edit existing files. Handy for a quick fix/typo correction. New files are not supported (yet, pull requests always welcome).
I'd like to, but Ruby is not one among my inventory...yet.
I didnt have luck importing any of my bitbucket public repositories.
@joelgm
Dunno why everyones mem usage is so low, our work one uses 6Gigs of ram. Guess it's due to the number of commits + activity?
Thanks, worked manually.
Gitlab is hard to install
Totally checking this out later tonight.
Yea man, copypasting is so difficult.
Took me few hours to install. I thought can be done under 1 hour
There's a Turnkey template for Gitlab which makes it incredibly easy to install.
Thanks. That's why I like host to have turnkey templates.
Optimizing the memory of gitlab is so painful. Took hours to research and try to lower down memory usage.
Mine was done in under twenty minutes. You can just take all those commands, insert them in a bash script and run it.
It does depend on activity. Git likes memory.
Took me quite some time the first time as well. You really need to read the instructions carefully and Ruby has some quirks from time to time. Now I know then ;-)
Anyway, good luck!
In the past installation and upgrade guides have been quite, lets say bad, cough shit cough. But, from 5.0 and upwards, every bonehead with root access is able to copypaste the steps and edit a hostname in a config file. That is literally all that needs to be done to either install or upgrade gitlab these days.
True, it was with a pre 5.x guide that it took me a while.
Steps like changing the gitlab user (username), moving from gitolite 2 to gitolite 3, then to gitlab shell, the a new ruby version. Seems they now've settled a bit. This upgrade replaced puma with unicorn, but except for the timeout I've not noticed any big issues in upgrading it...
Knowing Zero about Version control. Would this be useful for two users working on a project? What type of box should I look for to handle something like this? Changes would be a couple of files here and there daily. Total project would be 500-2GB in size.
For just two users a private github/gitorious would also be fine I think. Or just a git repo via ssh: https://raymii.org/s/tutorials/Shared_Git_repository_via_ssh_for_multiple_users.html
If you have "zero version control" knowledge it might be better to first read up on what Git is and what problems it can solve for you. Then you would be able to decide better if it helps you or not.
Isnt there an option to allow public gits to be viewed by non registered users (the general public)?
It might be a good thing if you have 0 knowledge of version control. Because coming from cvs/svn, git might be confusing
Any app of moderate complexity that uses Ruby will consume a lot of memory. There's no way around that. I've done a ton of web application development with PHP, Python, Perl, JavaScript, PostgreSQL, MySQL, etc and the apps I've come across that hog the most memory are invariably based on RoR.