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)
I am trying to cleanup Arch Linux package, remove some obsolete workarounds and make the directory structure more Linux idiomatic.
I see that there are 2 ruby files under /etc/webapps/gitlab - application.rb and boot.rb. It looks more like an application code than a config file. Folks, do you really modify these files? If yes - why do you do this, what kind of changes do you have?
If these files are never modified by a user then I better move it back to the application code directory.
secrets.yml missing entries & permission/ownership properties
Almost completed installation, version 13.1.4-1. Following changes had to be done to the secrets.yml file:
# chown root:gitlab /etc/webapps/gitlab/secrets.yml # chmod 640 /etc/webapps/gitlab/secrets.yml
production: secret_key_base: secret db_key_base: secret otp_key_base: secret openid_connect_signing_key: secret
4 different secrets were generated with hexdump as instructed in the wiki. Without these changes the command to initialize GitLab database failed:
$ cd /usr/share/webapps/gitlab $ sudo -u gitlab $(cat environment | xargs) bundle exec rake gitlab:setup
Missing Rails.application.secrets.otp_key_base for production environment. The secret will be generated and stored in config/secrets.yml. Missing Rails.application.secrets.openid_connect_signing_key for production environment. The secret will be generated and stored in config/secrets.yml. rake aborted! Errno::EACCES: Permission denied @ rb_sysopen - /usr/share/webapps/gitlab/config/secrets.yml
I did some small customisations to
gitlab.yml and did the whole setup using Saltstack configuration management, so didn't edit the wiki instructions yet as I'm not sure if these changes only apply to my setup.
I agree that this needs to be addressed.
The permissions on
/etc/webapps/gitlab/secrets.yml is wrong.
In my case, I let the
gitlab:setup take care of generating
openid_connect_signing_key, there for I had to do:
# chown root:gitlab /etc/webapps/gitlab/secrets.yml # chmod 660 /etc/webapps/gitlab/secrets.yml
But if you feel comfortable generating a
RSA PRIVATE KEY and dump it in the right place/format, you could do