Hacker News new | ask | show | jobs
by sytse 4922 days ago
Hi n0nick,

You're welcome, no problem that you are raising your opinion about the installation process, feedback will help make things better. The Phython dependency was there for a reason but I don't see it in the current installation doc so that is progress. The special users are due to using Gitolite, it is better to give it a separate unix user. The database requirement is needed unless you use SQlite, but support for this was dropped in 4.0 (and support for PostgreSQL made a lot better) because of the locking of SQlite. For sure GitLab is meant to run on a server and not on your development machine, did you get another impression from the readme description ('code hosting application')? What did you think it did?

1 comments

I haven't tried running it on my development machine; last time I tried installing it, it was on the server we use at work to host our git repositories.

Since it was already a dedicated server machine (which we even use sometimes to host some small web apps), I thought I had my work cut out for me.

It was the amount of system work required (sudo-ing, chmod-ing, installing mysql because we only used postgres before, creating users) that made me give up eventually.

I want to give GitLab another try, so I'll see into using Vagrant for that. But I still believe some install scripts would be very much appreciated and help the project gain popularity.

Btw, re Python - I still see the paragraph "Make sure you have the right version of Python installed" on: https://github.com/gitlabhq/gitlabhq/blob/4-0-stable/doc/ins...

You are right about Python still being required. I guess it is needed for syntax highlighting http://pygments.org/

I would recommend against using the Vagrant image for production, it is meant for development.

For production you can use a CentOS cookbook https://github.com/atomic-penguin/cookbook-gitlab or an Ubuntu script https://github.com/gitlabhq/gitlab-recipes/blob/master/insta...