Do you know how to set it up with Gitosis?
No, you'll probably have to modify some files to make it work. It looks like they only support gitolite.

Why do you want to stick with gitosis?
How about Gitorious?
I had installed it pretty easily.

PS.:I had written this earlier in this thread via mobile but somehow the post disappeared.
I wanted to stick with gitosis because:
1) I already have it installed.
2) I installed Gitolite, but when I tried to start GitLab, it kept complaining about some repositories or something that were made when Gitosis was installed.
I'll try again later.
Perhaps see this .

Here are some guides to migrate gitosis to gitolite.
I followed this guide to convert everything to GitoLite:

Now, when I try to make a new repository in GitLab, it asks me for the "git" user's password in the status update thing in command line that shows up when you run the command to start GitLab. I put in the right password, but, now, it just says this:
Quote:fatal: 'gitolite-admin' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

I just checked and there is the 'gitolite-admin.git' folder in /home/git/repositories
Everything is chmodded and chowned correctly.
Ah, nevermind. I give up.
Try this if you still feel like giving it a go

I still suggest cgit however. It's pretty easy to setup and doesn't need gitolite or gitosis or anything.
Looking back, I should have probably waited for you to reply before reinstalling.

Anyhow, thanks for all the help! I'll use this as future reference if I ever want to install GitLab again.
I'm pretty sure I have everything setup correctly, however, when I start the GitLab server, it says this:
[root@git gitlabhq]# bundle exec rails s -e production
=> Booting Thin
=> Rails 3.2.1 application starting in production on
=> Call with -d to detach
=> Ctrl-C to shutdown server
>> Thin web server (v1.3.1 codename Triple Espresso)
>> Maximum connections set to 1024
>> Listening on, CTRL+C to stop
/usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in `start_tcp_server': no acceptor (RuntimeError)
        from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in `start_server'
        from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/backends/tcp_server.rb:16:in `connect'
        from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/backends/base.rb:53:in `block in start'
        from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `call'
        from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
        from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
        from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
        from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
        from /usr/local/lib/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/handler/thin.rb:13:in `run'
        from /usr/local/lib/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/server.rb:265:in `start'
        from /usr/local/lib/ruby/gems/1.9.1/gems/railties-3.2.1/lib/rails/commands/server.rb:70:in `start'
        from /usr/local/lib/ruby/gems/1.9.1/gems/railties-3.2.1/lib/rails/commands.rb:55:in `block in <top (required)>'
        from /usr/local/lib/ruby/gems/1.9.1/gems/railties-3.2.1/lib/rails/commands.rb:50:in `tap'
        from /usr/local/lib/ruby/gems/1.9.1/gems/railties-3.2.1/lib/rails/commands.rb:50:in `<top (required)>'
        from script/rails:6:in `require'
        from script/rails:6:in `<main>'

However, it looks like GitLab starts anyways though. Does anyone know what's causing that?

EDIT: Nevermind I figured it out.

Users browsing this thread: 1 Guest(s)