Gitlab 5.0 released, Gitolite now gone • Hacker News Board

Re: Gitlab 5.0 released, Gitolite now gone

#91

Post by buster » Sat, Mar 23, 2013, 12:00 PM UTC

picomancer wrote: post #86

buster wrote: 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…

In another comment i mentioned installing apache, php, mysql and configuring all that as an ancient way that i was able to tolerate years ago, but not nowadays and not for a quick, single-user installation.

Nowadays you can easily have a webapp configure it self. I don't expect more then install/unpack, run, open browser, configure (in the browser), done! And the configure step shouldn't be much more then a) set up admin password and b) point so some database. And if i only want to evaluate or only want a single-user installation i don't want to install MySQL, i am fine with SQLite or HSQL or some other database that comes with the package.

Downloading a .tar.gz, unpacking to /var/www, editing apache config, editing htaccess, editing some config.php, restarting apache, continuing configuration in browser, installing a mailserver to send mails (wtf) is a rather common way i have seen in the PHP world. Gitlab just happened to make it even worse with post-install fixing known bugs/behaviour that should've been working out of the box.

Of course there are good examples and bad examples in each of those, it's surely not tied to the programming language that is used.

Re: Gitlab 5.0 released, Gitolite now gone

#92

Post by sytse » Sat, Mar 23, 2013, 2:48 PM UTC

rektide wrote: post #84

mbreese wrote: post #68

Earlier quoted context omitted.

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 thin…

FYI It is hard to use Gitolite config files in GitLab since GitLab already stores the configuration and premissions in the database.

Re: Gitlab 5.0 released, Gitolite now gone

#93

Post by sytse » Sat, Mar 23, 2013, 2:57 PM UTC

nonpme wrote: post #89

sytse wrote: post #79

Earlier quoted context omitted.

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.

Thanks nonpme, good to hear you are enjoying GitLab.

Re: Gitlab 5.0 released, Gitolite now gone

#94

Post by sytse » Sat, Mar 23, 2013, 3:00 PM UTC

rektide wrote: post #83

jameswritescode wrote: post #41

Earlier quoted context omitted.

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 reposit…

I'm sorry to hear we ruined your upcoming Monday. Which features are not in GitLab 5.0 that you really need?

Re: Gitlab 5.0 released, Gitolite now gone

#95

Post by rektide » Wed, Mar 27, 2013, 6:37 PM UTC

sytse wrote: post #92

rektide wrote: post #84

Earlier quoted context omitted.

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 thin…

FYI It is hard to use Gitolite config files in GitLab since GitLab already stores the configuration and premissions in the database.

thanks. my proposal was that perhaps there should be a script that can do much of the db configuration based off of what is in a gitolite.conf file.

Re: Gitlab 5.0 released, Gitolite now gone

#96

Post by rektide » Wed, Mar 27, 2013, 6:37 PM UTC

sytse wrote: post #94

rektide wrote: post #83

Earlier quoted context omitted.

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 reposit…

I'm sorry to hear we ruined your upcoming Monday. Which features are not in GitLab 5.0 that you really need?

Only feature missing from pre 5.0 is an upgrade path, but that's an important one for us.