This could take a while as it installs all required libraries.
# cd /home/gitlab/gitlab # source /home/gitlab/.bash_profile # sudo -u gitlab -H bundle install --deployment
Start redis server
Start the daemon. If you are using you might want to add
redis to your
DAEMONS array in
rc.d list redis.
Populate the database
# sudo -u gitlab bundle exec rake gitlab:app:setup RAILS_ENV=production
Setup gitlab hooks
# cp ./lib/hooks/post-receive /home/gitlab-git/share/gitolite/hooks/common/post-receive # chown gitlab-git:gitlab-git /home/gitlab-git/share/gitolite/hooks/common/post-receive
Server testing and resque process
Resque is a Redis-backed library for creating background jobs, placing those jobs on multiple queues, and processing them later. For the backstory, philosophy, and history of Resque's beginnings, please see this blog post.
Run resque process for processing queue:
# sudo -u gitlab bundle exec rake environment resque:work QUEUE=* RAILS_ENV=production BACKGROUND=yes
or use Gitlab's start script:
# sudo -u gitlab ./resque.sh
/home/gitlab/gitlab/tmp/pids/resque_worker.pidwill be owned by root causing the resque worker not to start via init script on next boot/service restart
Gitlab application can be started with the next command:
# sudo -u gitlab bundle exec rails s -e production
localhost:3000 with your favorite browser and you should see Gitlab's sign in page. In case you missed it, the default login/password are:
Since this is a thin web server, it is only for test purposes. You may close it with Template:Keypress. Follow instructions below to make Gitlab run with a real web server.