Live data from Hacker News

Gitlab 5.0 released, Gitolite now gone

blog.gitlab.org

81–90 of 96 posts

Re: Gitlab 5.0 released, Gitolite now gone

#81
post #78
post #75

Earlier quoted context omitted.

Some years back i was able to tolerate when a webapp needed serious fiddling in a) apache configs, b) php configs and c) manual mysql database setup. Nowaday i expect something to run and have as few steps to install as possible. It wasn't even so much the many steps in between but the stuff that just didn't work as given in the installation guide. Turned out that some answers were in the gitlab Troubleshooting Guide…

I'm sorry to hear you had trouble installing GitLab before. Installation should be a lot better now. We replaced resque with sidekick. Also there are pre installed images available from http://bitnami.com/stack/gitlab

Ah, sounds great. I think you should really advertise those packages more! To be honest the 5.0 installation guide still looks terribly long. No way i would go through that again. BUT now there are packages.. hopefully for 5.0 soon.

Re: Gitlab 5.0 released, Gitolite now gone

#82
post #81
post #78

Earlier quoted context omitted.

I'm sorry to hear you had trouble installing GitLab before. Installation should be a lot better now. We replaced resque with sidekick. Also there are pre installed images available from http://bitnami.com/stack/gitlab

Ah, sounds great. I think you should really advertise those packages more! To be honest the 5.0 installation guide still looks terribly long. No way i would go through that again. BUT now there are packages.. hopefully for 5.0 soon.

Good point. When the packages are updated to 5.0 I'll submit a merge request for the readme.

Re: Gitlab 5.0 released, Gitolite now gone

#83
post #40

Earlier quoted context omitted.

I don't think it's possible to use Gitolite with GitLab >= 5

You're correct. gitlab-shell is required in 5.

Welp, there goes an obvious good thing we had high hopes would help enrich our infrastructure! Monday is going to be a very depressing day in the office for everyone: we're going to have to go to cgit or some such, and there'll probably be screaming and crying and whaling and self flagellation over that one.

Ya'll should provide an easy to use configuration for using gitlab as a RO mirror of any arbitrary git repository.

Hope you have a lot of great new things in the pipe that gitlab-shell is providing. If configuration was the problem, why not try and scrape gitolite's configuration directly and run gitlab from that? There's certainly another acceptable path- the one you took, creating your own repo server- but I have a hard time qualifying this- as this press release does- as a feature: it's a migration, a lateral jump: there's nothing new that happens, nothing better, it's just a different configuration routine to do what Gitlab and Gitosis.

I wont be suckered by such suavity, but there's a lot of people who would be more enticed by "new super configurable way better than gitolite repo server" as a sales pitch that probably were happy enough running Gitlabs at it used to run that don't really see this as a feature, as they were already on top of it. When releasing features, put the featureful ones foremost.

Re: Gitlab 5.0 released, Gitolite now gone

#84
post #68
post #62

Last time i was installing gitlab after having the nightmare to install and maintain a gitorious installation and was really depressed that it felt like the same nightmare. Pages of pages of copy&paste instructions, followed by half a dozen issues that needed post-install fixing... no, never again.. I ended up installing gitblit and was amazed by the quick installation and features. Unpack&run! I can recommend gitbli…

I had the same issue a month or so ago. I needed to install a local Git repository and because I'd be working with people who had never used Git before, I wanted to have some kind of GUI for them. I looked at GitLab, Gitolite + gitweb, and Gitosis. GitLab's installation was the worst of the three. It was horrible, and seemed like it would have been impossible to maintain/upgrade. I really hope that the entire experie…

Gitolite- the old git repo for gitlab- is a cherished joy around here; we love it, it's both easy to use & has mad useful features. qa* users can commit to qa* branches? Sure, np.

I have a hard time sympathizing with Gitolite being removed for it's complexity. GitLab switching to their own stuff to make their side of the equation easier, to make their software less complex to write and configure, otoh might be a thing. I'd just need nominated yesterday to start trying to install it alongside Gitolite!

I wonder if they made a crack at being able to read and parse gitolite.conf files and use those configs to power gitlab? That would've been a happier path for me personally for smoothing out gitlab configuration hell, more so than writing a new repo server that we're not likely to qualify & then adopt, not when Gitolite is our living beating heart.

Re: Gitlab 5.0 released, Gitolite now gone

#85

This is great news as Gitolite was the one thing that prevented me from giving Gitlab a try. What are the minimum requirements for a light Gitlab installation? I can't find any recommendations on the site. The thought of deploying Gitlab on a Linode 512 for $20 a month with virtually unlimited private repositories is very exciting.

I'm running Gitlab 4.1 with more-or-less the default installation instructions and very light usage currently. I'll upgrade to 5.0 in the near future. Here's what I'm seeing:

    $ top
      PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
     1616 gitlab    20   0 1851m 108m 7112 S   0.0 10.9   7:46.35 ruby1.9.1
     1405 gitlab    20   0  967m  99m 7044 S   0.0 10.0   0:26.63 ruby1.9.1
     1667 gitlab    20   0  970m  98m 2596 S   0.0  9.9   0:01.36 ruby1.9.1
     1670 gitlab    20   0  970m  97m 2488 S   0.0  9.9   0:00.77 ruby1.9.1

    $ ps aux | grep [g]itlab
    USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
    gitlab    1405  0.0 10.0 990904 101508 ?       Sl   Mar19   0:26 unicorn_rails master -c /home/gitlab/gitlab/config/unicorn.rb -E production
    gitlab    1616  0.1 10.9 1896392 110880 ?      Sl   Mar19   7:46 sidekiq 2.6.4 gitlab [0 of 25 busy]
    gitlab    1667  0.0  9.9 994156 100412 ?       Sl   Mar19   0:01 unicorn_rails worker[0] -c /home/gitlab/gitlab/config/unicorn.rb -E production
    gitlab    1670  0.0  9.9 994204 100284 ?       Sl   Mar19   0:00 unicorn_rails worker[1] -c /home/gitlab/gitlab/config/unicorn.rb -E production
This doesn't include Redis or database.

It seems like that's far too high. Why do you need 400MB of runtime data (and 5GB of allocation) in order to generate these relatively simple web pages?

Ruby is bloated.

Re: Gitlab 5.0 released, Gitolite now gone

#86
post #62

Last time i was installing gitlab after having the nightmare to install and maintain a gitorious installation and was really depressed that it felt like the same nightmare. Pages of pages of copy&paste instructions, followed by half a dozen issues that needed post-install fixing... no, never again.. I ended up installing gitblit and was amazed by the quick installation and features. Unpack&run! I can recommend gitbli…

Installation is actually a problem with Rails, and web app development as a whole.

Think about PHP: Drop files in the web server directory, add a database and user, edit the app configuration file to point to said database and user, and you're done.

Then there's Rails apps. Gitolite is actually fairly typical: Install a ton of packages (including ssh, redis, and postfix daemons which need to be secured), compile your own Ruby (and keep it up to date), install the Bundler gem, configure Gitlab, configure Gitlab shell, configure Unicorn, configure the database, install gems with bundler, bundle exec rake gitlab:setup RAILS_ENV=production (I have no idea what this does), install an init script, update your rc.d, then set up an nginx reverse proxy [1].

If you're used to setting up web apps, this is typical, and very well-described by the provided instructions. If you're used to the PHP experience, or you've only ever installed distro-packaged apps with apt-get or equivalent, this process feels really unreasonably long and painful.

I remember that the Discourse folks said that they were aware that installation was a pain point, and they were working on making it easier.

Lowering the barriers to installation is actually something that web applications written in Ruby/Python/Node.js really need to do in order to begin to compete with PHP solutions among more casual administrators.

A big part of the problem is isolation from the system package manager. I have a Redmine install on the same server as Gitolite, which I manage via apt-get. I'd really like to have a version of the Gitlab instructions that keeps non-system packages (like the self-compiled Ruby) self-contained in /home/git, so they don't break anything else.

[1] https://github.com/gitlabhq/gitlabhq/blob/5-0-stable/doc/ins...

Re: Gitlab 5.0 released, Gitolite now gone

#87
post #62

Last time i was installing gitlab after having the nightmare to install and maintain a gitorious installation and was really depressed that it felt like the same nightmare. Pages of pages of copy&paste instructions, followed by half a dozen issues that needed post-install fixing... no, never again.. I ended up installing gitblit and was amazed by the quick installation and features. Unpack&run! I can recommend gitbli…

Installation is actually a problem with Rails, and web app development as a whole. Think about PHP: Drop files in the web server directory, add a database and user, edit the app configuration file to point to said database and user, and you're done. Then there's Rails apps. Gitolite is actually fairly typical: Install a ton of packages (including ssh, redis, and postfix daemons which need to be secured), compile your…

...compete with PHP, seriously?

Many of the points above apply to any language. Ruby might have maintainability issue but PHP is far far from perfect.

Re: Gitlab 5.0 released, Gitolite now gone

#88
post #62

Last time i was installing gitlab after having the nightmare to install and maintain a gitorious installation and was really depressed that it felt like the same nightmare. Pages of pages of copy&paste instructions, followed by half a dozen issues that needed post-install fixing... no, never again.. I ended up installing gitblit and was amazed by the quick installation and features. Unpack&run! I can recommend gitbli…

Installation is actually a problem with Rails, and web app development as a whole. Think about PHP: Drop files in the web server directory, add a database and user, edit the app configuration file to point to said database and user, and you're done. Then there's Rails apps. Gitolite is actually fairly typical: Install a ton of packages (including ssh, redis, and postfix daemons which need to be secured), compile your…

[deleted]

Re: Gitlab 5.0 released, Gitolite now gone

#89
post #79
post #66

Earlier quoted context omitted.

Is 1GB really requred for personal use? I thought about buying 256/512 VPS exclusively for GitLab, don't you think it will be enough for personal projects? Maybe someone who has the knowledge can write tutorial about configuring GL to run on average VPS?

A post about tuning GitLab for low memory consumption would be very useful indeed.

Maybe someone will write one someday ;).

And, as I have the chance, I want to thank you and whole GitLab team for a really great work! I'm using GL localy and I'm very pleased with it.

Re: Gitlab 5.0 released, Gitolite now gone

#90
post #87

Earlier quoted context omitted.

Installation is actually a problem with Rails, and web app development as a whole. Think about PHP: Drop files in the web server directory, add a database and user, edit the app configuration file to point to said database and user, and you're done. Then there's Rails apps. Gitolite is actually fairly typical: Install a ton of packages (including ssh, redis, and postfix daemons which need to be secured), compile your…

...compete with PHP, seriously? Many of the points above apply to any language. Ruby might have maintainability issue but PHP is far far from perfect.

The point is very valid.

The person who has to install some third party web application is mainly concerned with “how easy is this to install”.

Not only have I steered clear of installing things with too many alien prerequisites, I’m often writing in PHP only because deployment is just so much easier.

Post reply on HN