Difference between revisions of "Talk:Gitlab"

From ArchWiki
Jump to: navigation, search
m
Line 47: Line 47:
 
:: I have done some work on the article to update it for 5.2. This is mostly how I currently use it (I have also added an rvm section that reflects my current environment). I would be happy if someone could review it to make sure it contains no errors and works this way. It is still not finished. For example, I noticed a hint during the unicorn section to restart the systemd services which are not yet present at this time during the configuration. Since unicorn got replaced anyway it may be a good idea to remove or reword that section. I found that I did not need to edit anything for puma so maybe it is a good idea to drop this completely? Also I did not yet include any "requires" yet and my sidekiq unit looks different because I use the original commands (I don't understand yours. If it is more suited, maybe you could explain it?). [[User:Javex|Javex]] ([[User talk:Javex|talk]]) 21:13, 23 May 2013 (UTC)
 
:: I have done some work on the article to update it for 5.2. This is mostly how I currently use it (I have also added an rvm section that reflects my current environment). I would be happy if someone could review it to make sure it contains no errors and works this way. It is still not finished. For example, I noticed a hint during the unicorn section to restart the systemd services which are not yet present at this time during the configuration. Since unicorn got replaced anyway it may be a good idea to remove or reword that section. I found that I did not need to edit anything for puma so maybe it is a good idea to drop this completely? Also I did not yet include any "requires" yet and my sidekiq unit looks different because I use the original commands (I don't understand yours. If it is more suited, maybe you could explain it?). [[User:Javex|Javex]] ([[User talk:Javex|talk]]) 21:13, 23 May 2013 (UTC)
  
::: That looks good :) The web server section needs a complete rewrite. I didn't know mtorromeo had PKGBUILDs for GitLab! I'll check them for sure.
+
::: That looks good :) The web server section needs a complete rewrite. I didn't know mtorromeo had PKGBUILDs for GitLab! I'll check them for sure. --[[User:Maevius|Maevius]] ([[User talk:Maevius|talk]]) 14:44, 24 May 2013 (UTC)

Revision as of 14:44, 24 May 2013

Out of date

Note: these instructions are for the older version of gitlab. Use of resque is depricated. These instruction should be updated. I'm not sure how to get the new initscripts working on arch though.. 00:58, 14 February 2013‎ Archguy

Yeap! I'm aware of the new changes. Also 5.0 is coming and gitlab will no longer need gitolite. The whole article needs an update. As for initscripts, if you take a look at the issue tracker there are systemd files provided. I will clean it up when 5.0 comes out. Also Archguy, please remember to sign your posts by typing four tildes (~~~~) at the end. --Maevius (talk) 05:58, 14 February 2013 (UTC)

unicorn replaced by puma

I noticed today that for 5.2 puma replaced unicorn. On the same matter, I had to update my systemd file since puma is forking and not simple. Should I edit the Wiki for the new version? Also it seems not everything is up2date yet in this article. Can I help somewhere? Javex (talk) 20:53, 22 May 2013 (UTC)

Actually unicorn is replaced by puma since 5.1. I haven't edited the whole article yet, I reached till the web server configuration. If you think you can help then by all means do it! Can you share your systemd files as well? Here is what I got so far, but sidekiq is timing out. They are probably missing the Requires and After attributes since redis must be running for sidekiq to work.
gitlab-puma.service

[Unit]
Description=GitLab Puma Server

[Service]
User=git
WorkingDirectory=/home/git/gitlab
Environment=RAILS_ENV=production
ExecStart=/usr/bin/bundle exec "puma -C /home/git/gitlab/config/puma.rb -e production"
SyslogIdentifier=gitlab-puma
Type=forking
PIDFile=/home/git/gitlab/tmp/pids/puma.pid

[Install]
WantedBy=gitlab.target

gitlab-sidekiq.service
[Unit]
Description=GitLab Sidekiq Server

[Service]
User=git
WorkingDirectory=/home/git/gitlab
Environment=RAILS_ENV=production
ExecStart=/usr/bin/bundle exec "sidekiq -q post_receive,mailer,system_hook,project_web_hook,gitlab_shell,common,default -e production -P /home/git/gitlab/tmp/pids/sidekiq.pid"
SyslogIdentifier=gitlab-sidekiq
Type=forking
PIDFile=/home/git/gitlab/tmp/pids/sidekiq.pid

[Install]
WantedBy=gitlab.target

--Maevius (talk) 06:17, 23 May 2013 (UTC)

I have done some work on the article to update it for 5.2. This is mostly how I currently use it (I have also added an rvm section that reflects my current environment). I would be happy if someone could review it to make sure it contains no errors and works this way. It is still not finished. For example, I noticed a hint during the unicorn section to restart the systemd services which are not yet present at this time during the configuration. Since unicorn got replaced anyway it may be a good idea to remove or reword that section. I found that I did not need to edit anything for puma so maybe it is a good idea to drop this completely? Also I did not yet include any "requires" yet and my sidekiq unit looks different because I use the original commands (I don't understand yours. If it is more suited, maybe you could explain it?). Javex (talk) 21:13, 23 May 2013 (UTC)
That looks good :) The web server section needs a complete rewrite. I didn't know mtorromeo had PKGBUILDs for GitLab! I'll check them for sure. --Maevius (talk) 14:44, 24 May 2013 (UTC)