From ArchWiki
Jump to: navigation, search

Missing Section?

It might just be me, but it seems like a section is missing. In start and test it says visit your domain, however unless I am missing something pretty major that shouldn't work since neither apache nor nginx are ever setup / pointed to the webapp.--Theflyingfool (talk) 08:15, 8 April 2014 (UTC)

I don't have neither of them on my server, Gitlab uses own one, Unicorn, to deal with webapp. Kosciak9 (talk) 12:17, 6 December 2015 (UTC)

Resolving dependencies and testing gitlab on remote server

This is a reply to the question above, as well some things that was missed during the installation I made.

I'm not sure if it should be added, so I'm putting it here for discussion:

You should install the following packages, before installing the GitLab from AUR:

Also, after finally starting the gitlab with unicorn, if you have installed gitlab on a remote server and not locally, you won't be able to access it using domain:8080. It is even mentioned in /etc/webapps/gitlab/unicorn.rb. In order to be able to access it, I have changed to the servers IP, and made sure that shell.yml reflect the change as well (including the port).

After restarting the daemons, I was able to access giltab using domain:8080.

Tahvok (talk) 09:18, 15 May 2014 (UTC)


After completing the steps above I continued to nginx installation, however, being not familiar with nginx it took me some time, so I'll put it here for discussion as well. This is the full guide, I know that some things are already mentioned in the page, just not very organized.

After installing nginx, it is mentioned that you should make the following command:

# ln -s /etc/nginx/sites-available/gitlab /etc/nginx/sites-enabled/gitlab

However, it will not work, since there is no site-available or sites-enabled directories, with include section in nginx.conf. It is true however in debian installations, but since we're in arch everything comes with no changes from the distro side.

Since there was no site-available file to copy the vhosts from, I read the official gitlab guide, and found that the file is located in /usr/share/webapps/gitlab/lib/support/nginx/ after installing the gitlab package.

I just put everything inside the file to nginx.conf inside the http section, just before the last }, and changed the following:

  • server_name to reflect my server's domain.
  • Set proxy_pass config to reflect unicorn listening address. I just put localhost:8080 in nginx.conf and set back unicorn.rb to point to as it was before (including the port 8080).
  • Inside upstream gitlab set server to point to unix:/usr/share/webapps/gitlab/tmp/sockets/gitlab.socket; - I'm NOT sure about this. I also had a permissions problem, so I changed group permission to http for the sockets folder.
  • Point the config root to /usr/share/webapps/gitlab/public;
  • Comment out the gzip section - it was not working for me, and made the site with no assets, so I didn't bother with it.

Edit shell.yml as follows:

gitlab_url: "http://domain/" - domain is the same as server_name in nginx.conf.

Also make sure that in gitlab.yml the host is set to your domain and the port is the same as in nginx.conf.

Restart the daemons:

$ systemctl restart gitlab-sidekiq gitlab-unicorn nginx

Should be working now.

As I said, this is my rough way of installing it, so before I put it on the page, would like to know if that's the right steps.

Tahvok (talk) 09:18, 15 May 2014 (UTC)

Ruby Version

Since gitlab does not support ruby 2.2 yet (see : I do get 500 errors on most operations), it seems it would be nice to amend this tutorial to state this fact and to explain how to install from 2.1. —This unsigned comment is by Pascal.vanier (talk) 2015-03-17. Please sign your posts with ~~~~!

Satelites are removed

The satalites are no longer used in a gitlab instance since 24-09-'15. IMO the section could be removed. —This unsigned comment is by Salamandar (talk) 11:00, 6 December 2015‎. Please sign your posts with ~~~~!

The Aur package still creates the directory. --Indigo (talk) 23:14, 7 April 2016 (UTC)

Ruby 2.1 or 2.2 ?

Well, the AUR package needs the ruby2.1 package. BUT the wiki is about ruby2.2. That would be better to agree on this :p

—This unsigned comment is by Salamandar (talk) 10:56, 6 December 2015‎. Please sign your posts with ~~~~!

According to the official documentation, only Ruby 2.1 is supported. -- Lonaowna (talk) 15:52, 8 April 2016 (UTC)

Using Sudo instead of su -

I don't have any root password on my pi, only my user password (for sudo). As the rest of the documentation uses sudo, it would be better to use sudo here too :

For some reason all sudo - commands fail for me, not sure why. ElectricPrism (talk) 08:10, 21 December 2015 (UTC)

I'm also having issues without being root, unfortunately there are more issues, and I couldn't install (the latest version) at all.
Going to add Stub template, because more commands listed doesn't seem to work (correctly).
Beta990 (talk) 11:42, 21 December 2015 (UTC)
Note: Regarding the `su - gitlab` users have gotten a update because they kept failing for me too.



About the letsencrypt section you have remove from the wiki. You are right, most of the part are covered by the wiki, but one things that take me some time to bypass :)

letsencrypt check on your webserver if a well-known file is available. Something like :

But, due to apache configuration, this request is given to the gitlab proxy that don't know how to handle that. That's why I add the following in my conf

 Alias "/.well-known"  "/srv/http/letsencrypt/.well-known"                                                                                                                                                    
 RewriteCond   %{REQUEST_URI}  !/\.well-known/.*

That's the only part that is gitlab only. Ok, it's not may be well explain. And, btw, as I'm new to wiki contribution, this is may be not the right place to discuss that....

Anyway, this little modification take me some times to figure out, and having it on the wiki, or any other better ones can be a benefit

hanks for responding. That little bit of explanation helps to understand why it's needed, so feel free to modify the article and add that explanation and configuration to that section. Rdeckard (talk) 17:22, 21 March 2016 (UTC)
Looks better to you now ? Mfc alpha (talk) 17:39, 21 March 2016 (UTC)
Overall looks good. It just needed that extra little bit of info you provided. I did make a change for some formatting and style (see Help#Style). Feel free to continue to make more changes. Closing, but feel free to open again if you have questions or issue. Thanks! Rdeckard (talk) 19:07, 21 March 2016 (UTC)

Very confusing

I went through the install, I didn't make it work yet but I have a few questions on confusing instructions:

-I want to use my already set-up nginx webserver. Should I still use reddis, and the gem/bundle install commands ?

Yes, you should proxy-pass nginx to unicorn. Redis is used for internal communication, gem/bundle for setup. You can find good explanations at the GitLab website. DenBrahe (talk) 21:43, 19 April 2016 (UTC)

-What are the pros/cons to use the AUR package v. using the official package ?

AUR package is finetuned for Arch to work with systemd and linux conventions and things like that (don't know exactly). Basically if you're not an expert, you're better off with the AUR package. Wiki page should get an update though. DenBrahe (talk) 21:43, 19 April 2016 (UTC)

-How can we uninstall the components installed by the gem/bundle install commands ?

-the su - gitlab command is not working but sudo -u gitlab works (as mentionned in this thread), is that ok ?

-I don't have any shell.yml file, which is mentionned only once for the HTTPS configuration, is it normal ?

-what is /dev/null in the nginx config ?

-how do I setup resque.timer ? I can't load it? ('unit resque.timer not found).

Mentatf (talk) 22:41, 7 April 2016 (UTC)