WebFaction
Community site: login faq
0
1

I have already referred the below links and read the commands: http://community.webfaction.com/questions/7958/gitolite-and-gitlab http://community.webfaction.com/questions/5995/i-would-like-to-install-gitlabhq-on-webfaction

I want to know if there is 1 single guide for installing gitlabhq in webfaction. Both of the above links provides great commands but all scattered and not in order.

Is there a full consolidated version in one single order? Also after executing these commands has anyone been successful to install gitlabhq.

asked 14 May '12, 01:51

talktoari's gravatar image

talktoari
525
accept rate: 0%


The answer by ArrantSquid here is the most up-to-date guide as of now.
I am sure that he was successful in installing Gitlab using those.
Have you tried it yet?

permanent link

answered 14 May '12, 02:05

neeravk's gravatar image

neeravk
1.5k3411
accept rate: 41%

Thanks for your response.

No I haven't tried it yet but I have gone through the guide. I just wanted to make sure that if I start and follow that in order, I will be able to get it up and running in my web faction account. Let me know.

  1. Do I select Rails as the app while trying to create a new app in my web faction account?
  2. By default web faction has ruby 1.9.3 for the latest choice of rails app. Shall I chose that or do a custom installation of ruby 1.9.2p0?
  3. Will I be able to install all the libraries and packages needed or are they already installed in webfaction?
(14 May '12, 02:26) talktoari talktoari's gravatar image

Do I select Rails as the app while trying to create a new app in my web faction account?

No, you need to select a custom app(listening on port) for the new app. You would also need to make one more to reserve a port for your redis installation

By default web faction has ruby 1.9.3 for the latest choice of rails app. Shall I chose that or do a custom installation of ruby 1.9.2p0?

I have not personally tried with 1.9.3 that is installed but Gitlab itself recommends Ruby 1.9.2

https://github.com/gitlabhq/gitlabhq/blob/master/doc/installation.md

Will I be able to install all the libraries and packages needed or are they already installed in webfaction?

Yes, the installation covers all the needed packages already.

(14 May '12, 02:37) neeravk neeravk's gravatar image

Thanks Neerav. I will follow that whole process and will ask if any problems faced.

(14 May '12, 04:51) talktoari talktoari's gravatar image

Everything worked fine till the step: bundle install --without development test

After that when I run: bundle exec rake db:setup RAILS_ENV=production

I get an error:

Access denied for user 'root'@'localhost' (using password: YES). Please provide the root password for your mysql installation

rake aborted! Access denied for user 'root'@'localhost' (using password: YES)

Tasks: TOP => db:setup => db:schema:load_if_ruby => db:create (See full trace by running task with --trace)

After that i created a new DB from the webfaction control panel and then I edited my config/database.yml file to change the prod env to use the current db and db_user. Now i get the error:

[gitlab@web301 gitlabhq]$ bundle exec rake db:setup RAILS_ENV=production dnsoft_gitlabhq already exists rake aborted! ERR operation not permitted

Tasks: TOP => db:schema:load => environment (See full trace by running task with --trace)

What should be done to resolve this problem? How can I run the "rake db:setup" command?

Also i did not understand your comment, "You would also need to make one more to reserve a port for your redis installation" How do I make my redis use the custom port?

Last question, If I logout / close my ssh session to the current ssh user, since gitosis is running, when I issue ssh gitlab_user@server.com I could not go and login to the home dir of my gitlab_user. I get an error about PTY not free for channel 0 or something. How can I login to my home dir and continue the steps further?

(14 May '12, 14:26) talktoari talktoari's gravatar image

What should be done to resolve this problem? How can I run the "rake db:setup" command?

Can you run with --trace and copy the full trace here?

Also i did not understand your comment, "You would also need to make one more to reserve a port for your redis installation" How do I make my redis use the custom port?

You need to specify that in your redis.conf, you need to edit the "port 6379" line.

Last question, If I logout / close my ssh session to the current ssh user, since gitosis is running, when I issue ssh gitlab_user@server.com I could not go and login to the home dir of my gitlab_user. I get an error about PTY not free for channel 0 or something. How can I login to my home dir and continue the steps further?

You need to login as your main user then do: "su - gitlab" to login as gitlab.

(14 May '12, 22:51) neeravk neeravk's gravatar image

Thanks Neerav. Here is what I have done and still get the error.

  1. Used "su" to go to gitlab user.
  2. Create a new custom app with listening port
  3. Modified the ~/redis.conf file and added the above apps port number in the file
  4. Ran the command: bundle exec rake db:setup RAILS_ENV=production --trace

Here is the error:

Invoke db:setup (first_time) Invoke db:schema:load_if_ruby (first_time) Invoke db:create (first_time) Invoke db:load_config (first_time) Invoke rails_env (first_time) Execute rails_env Execute db:load_config Execute db:create dnsoft_gitlabhq already exists Execute db:schema:load_if_ruby Invoke db:schema:load (first_time) Invoke environment (first_time) Execute environment rake aborted! ERR operation not permitted /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/redis-2.2.2/lib/redis/client.rb:47:in call' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/redis-2.2.2/lib/redis.rb:435:inblock in sadd' /home/gitlab/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:in mon_synchronize' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/redis-2.2.2/lib/redis.rb:434:insadd' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/redis-namespace-1.0.3/lib/redis/namespace.rb:213:in method_missing' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/resque-1.20.0/lib/resque.rb:205:inwatch_queue' /home/gitlab/gitlabhq/config/initializers/gitlabhq/30_resque_queues.rb:1:in <top (required)>' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:245:inload' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:245:in block in load' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:236:inload_dependency' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:245:in load' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/engine.rb:588:inblock (2 levels) in <class:engine>' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/engine.rb:587:in each' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/engine.rb:587:inblock in <class:engine>' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/initializable.rb:30:in instance_exec' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/initializable.rb:30:inrun' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/initializable.rb:55:in block in run_initializers' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/initializable.rb:54:ineach' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/initializable.rb:54:in run_initializers' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/application.rb:136:ininitialize!' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/railtie/configurable.rb:30:in method_missing' /home/gitlab/gitlabhq/config/environment.rb:5:in<top (required)="">' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:251:in require' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:251:inblock in require' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:236:in load_dependency' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.2.3/lib/active_support/dependencies.rb:251:inrequire' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/application.rb:103:in require_environment!' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/railties-3.2.3/lib/rails/application.rb:292:inblock (2 levels) in initialize_tasks' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:in call' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:inblock in execute' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:in each' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:inexecute' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:158:in block in invoke_with_call_chain' /home/gitlab/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:inmon_synchronize' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:151:in invoke_with_call_chain' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:176:inblock in invoke_prerequisites' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:174:in each' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:174:ininvoke_prerequisites' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:157:in block in invoke_with_call_chain' /home/gitlab/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:inmon_synchronize' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:151:in invoke_with_call_chain' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:144:ininvoke' /home/gitlab/.rvm/gems/ruby-1.9.2-p290/gems/activerecord-3.2.3/lib/active_record/railties/databases.rake:373:in block (3 levels) in <top (required)>' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:incall' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:205:in block in execute' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:ineach' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:200:in execute' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:158:inblock in invoke_with_call_chain' /home/gitlab/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:in mon_synchronize' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:151:ininvoke_with_call_chain' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:176:in block in invoke_prerequisites' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:174:ineach' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:174:in invoke_prerequisites' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:157:inblock in invoke_with_call_chain' /home/gitlab/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/monitor.rb:201:in mon_synchronize' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:151:ininvoke_with_call_chain' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/task.rb:144:in invoke' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:116:ininvoke_task' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:in block (2 levels) in top_level' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:ineach' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:94:in block in top_level' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:133:instandard_exception_handling' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:88:in top_level' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:66:inblock in run' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:133:in standard_exception_handling' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/lib/rake/application.rb:63:inrun' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/gems/rake-0.9.2.2/bin/rake:33:in <top (required)>' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/bin/rake:19:inload' /home/gitlab/.rvm/gems/ruby-1.9.2-p290@global/bin/rake:19:in `<main>' Tasks: TOP => db:schema:load => environment

(15 May '12, 01:21) talktoari talktoari's gravatar image

The problem appears to be of the redis server. Tried the below command: [gitlab@web301 gitlabhq]$ redis-cli ping

(error) ERR operation not permitted

Also looks like redis is still running on port 6379. The redis-cli shows the same.

[gitlab@web301 gitlabhq]$ redis-cli

redis 127.0.0.1:6379> exit

How can this be rectified to have my bundle exec rake db:setup work fine?

(15 May '12, 01:56) talktoari talktoari's gravatar image

Yes, it seems your redis server is not running, can you start it and then try the rake command?

(15 May '12, 02:15) neeravk neeravk's gravatar image

I had executed the command

redis-server /home/gitlab/redis.conf

Also verified that ps -ef | Grep redis listed my command

But it is giving the same error

(15 May '12, 04:51) talktoari talktoari's gravatar image

Also looks like redis is still running on port 6379. The redis-cli shows the same.

[gitlab@web301 gitlabhq]$ redis-cli

redis 127.0.0.1:6379> exit

That is actually someone else's redis that they are running on the default port.

You can verify yours is working correctly by:

redis-cli -p $YOURPORT ping

If this is working, you need to run:

export REDIS_URL=redis://127.0.0.1:<YOURPORT>/0

before running your rake command.

(15 May '12, 05:09) neeravk neeravk's gravatar image

Thanks a lot Neerav. Your guidance is really helpful.

This command responded with "PONG" confirming the redis for my port is running fine.

redis-cli -p $YOURPORT ping

Ran the export command and then the rake commands and all worked fine.

export REDIS_URL=redis://127.0.0.1:<YOURPORT>/0

Even ran the below commands and all worked OK

bundle exec rails s -e production -p <your_custom_port> -d
$HOME/gitlabhq/resque.sh

After this I linked this app to the subdomain I had added earlier. I had mapped it to "/".

Tried opening:

<app-name>.<username>.webfactional.com

It asked for username and password. Provided the username and password as created by db:seed_fu

And my homepage opens for gitlabhq. But there is one problem:

As soon as I click new project, it gives me an error saying page cannot be found. not sure what is the problem here. If all login and homepage and even admin profile is visible then what could go wrong?

(15 May '12, 06:22) talktoari talktoari's gravatar image

Looks like the projects/new link does not work fine. I want ask whether webfaction has a plan to have a 1-click install for gitlabhq in near future?

(15 May '12, 13:00) talktoari talktoari's gravatar image

We do not have any plans to add this to our supported installers. You may submit a support ticket if you would like us to investigate further.

(15 May '12, 18:15) johns ♦♦ johns's gravatar image
showing 5 of 13 show 8 more comments

I documented the steps I took to get gitlab working...

https://gist.github.com/mogga/5da4b5ed8f994a036607

permanent link

answered 09 Nov '14, 02:25

mogga's gravatar image

mogga
213
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×106
×9
×5

question asked: 14 May '12, 01:51

question was seen: 4,918 times

last updated: 09 Nov '14, 02:25

WEBFACTION
REACH US
SUPPORT
AFFILIATE PROGRAM
LEGAL
© COPYRIGHT 2003-2016 SWARMA LIMITED - WEBFACTION IS A SERVICE OF SWARMA LIMITED
REGISTERED IN ENGLAND AND WALES 5729350 - VAT REGISTRATION NUMBER 877397162
5TH FLOOR, THE OLD VINYL FACTORY, HAYES, UB3 1HA, UNITED KINGDOM