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)
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 : https://wiki.archlinux.org/index.php?title=Gitlab§ion=13
- 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)
- From what I've seen online, the correct way of sudo'ing into the gitlab user would be `sudo -i -u gitlab /bin/sh` but that results in a `Only ssh allowed` error for me (which I think originates from gitab-shell).
- You can always do `sudo su - gitlab -s /bin/sh`, that does work for me.
- Gtarsia (talk) 18:23, 31 January 2019 (UTC)
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).
I am adding my two cents to this section as well, because after trying for around 5 hours, I am giving up on the gitlab package and will try Gogs/Gitea instead. As I cannot say for sure what are actual problems and which are design choices made by the package maintainer that are just not well documented, someone else who has the necessary knowledge has to decide which changes are appropiate to make.
This is summary of the problems/confusion I faced:
- The package depends on ruby2-3, which does not provide the bin 'ruby'. This throws off the environment check at the very least, yet no note is made of that.
- Despite stating that the Arch package uses the user gitlab instead of git, the latter keeps getting mentioned in the article, sometimes even together with gitlab.
- As described below, rvm seems to be neither necessary nor supported, yet the article implies that its usage is good practise.
- All GitLab files seem to belong to root, leaving the gitlab with insufficient rights to save config files. As a result, at the very least the copy&paste solutions provided by the environment checks cannot be used because of that.
- The article states that Unicorn is a HTTP server on its own, yet GitLab is shipped with nginx by default.
- The article says that gitlab-workhorse is optional, yet at the very least the current Apache examples provided by GitLab all assume it to be configured. The package itself also depends on it.
Right now, it might be a better idea to intall GitLab from source, as the official documentation is more up-to-date and can be used with less adjustments. --Krukai (talk) 09:15, 8 September 2017 (UTC)
Another small thing: the wiki page says we should enable
gitlab-unicorn services, but these are already part of
gitlab.target, so I believe there is no need in enabling them separately. --Nplatis (talk) 06:04, 26 September 2017 (UTC)
Check that the secret file exists
The Initialize Gitlab database section tells us to check if there's a secret file at /etc/webapps/gitlab/secret, while the file is found at /etc/webapps/gitlab/secrets.yml now. Sava (talk) 08:21, 25 September 2016 (UTC)
Rewrite of the article
Hello everyone. If I look at your comments, we clearly see there is an issue with this installation guide. I talked on IRC with Sven-Hendrik Haase, the maintainer of the
gitlab package, and it seems only him has abilities to make this package 'work' properly without issue. Being the packager and knowing how Gitlab internals working is clearly an advantage, but this isn't the case for the newbie/simple Arch Linux user just wanting to have Gitlab installed in a matter of minutes. This is why I decided to completely rewrite this page. Please let me know your idea and comments wrt. this rewrite. New commits are ongoing. -- wget (talk) 13:46, 19 November 2017 (UTC)
- I've also recently successfully set up Gitlab using the Arch packages. There are a couple of things specific to my setup which are not mentioned on this page, but overall I don't see a need for a rewrite. It would also be hard to impossible to compare the differences from the current page. If you do that anyway, please use your user page for the draft. -- Lahwaacz (talk) 15:02, 19 November 2017 (UTC)
- What I mean by rewrite, the structure won't change, this is basically the same but all sentences have been reworded, because when you come along as a newbie, the package split seems weird and you do not know the different parts that constitutes Gitlab. But anyway, no worry, I can use this page is you want me to. I'm quite used in rewriting article (VirtualBox for example is a topic I have rewritten two years ago, Odoo and Mattermost as well). Since you're here, I have a question I would' like to ask you wrt. MediaWiki syntax with ArchLinux specific templates. I used bullet points in my rewrite:
- I managed to have a working Gitlab instance! But I mostly followed the explanations from https://docs.gitlab.com/ee/install/installation.html… The ArchLinux Wiki is really outdated and also misguiding :-( But it still helped me out for the Arch-specific part (like the `sudo` to launch a command).
- - I believe there is a typo between `secret` and `secrets` (or Gitlab changed the name);
- - Nginx is now mandatory to serve the assets.
- IMHO the main interest of this package is to provide compiles assets, so you don't need nodejs & go. However, if I had to install it again from scratch, I surely will try to use the Gitlab procedure. Mdhooge (talk) 09:36, 23 July 2018 (UTC)
Old configuration info
Recently tried to setup gitlab/nginx by instructions on this page, but they are quite legacy for current version on community repository (config lines, locations, not-existent files). Any maintainer here? =)
- Corrections are always welcome so feel free to flag the inaccuracies with Template:Accuracy or just fix them if you know what is correct. As for the config snippets, I think they are mostly unnecessary as the default files are heavily commented, so it would be enough to describe what to look for. -- Lahwaacz (talk) 22:37, 4 December 2017 (UTC)
- Indeed this article is a nightmare. I'm currently completely rewriting it, but I'm only able to work an hours a day on it. The rest of my FOSS time is devoted to maintaining some AUR packages. Please continue noticing issues about Gitlab on Arch Linux or simply modifying this document. I'm taking actions. :) -- wget (talk) 23:03, 4 December 2017 (UTC)