Difference between revisions of "Gitlab2"

From ArchWiki
Jump to: navigation, search
(Setup gitlab hooks: Not needed anymore.)
(Server testing and resque process: Gitlab4.1 Replaced Resque with Sidekiq. See http://blog.gitlab.org/gitlab-4-1-released/.)
Line 9: Line 9:
  
 
==Gitlab==
 
==Gitlab==
 
===Server testing and resque process===
 
 
[http://defunkt.io/resque/ 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 [https://github.com/blog/542-introducing-resque 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
 
 
{{Note|If you run this as root, {{ic|/home/gitlab/gitlab/tmp/pids/resque_worker.pid}} will 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
 
 
Open {{ic|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:
 
 
login.........admin@local.host
 
password......5iveL!fe
 
 
Since this is a thin web server, it is only for test purposes. You may close it with {{Keypress|Ctrl+c}}. Follow instructions below to make Gitlab run with a real web server.
 

Revision as of 10:40, 10 June 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary end

Merge-arrows-2.pngThis article or section is a candidate for merging with Gitlab.Merge-arrows-2.png

Notes: Most of the text are the same. (Discuss in Talk:Gitlab2#)

Gitlab