change gitlab.target to gitlab.service

This commit is contained in:
Praveen Arimbrathodiyil 2017-02-15 11:31:43 +05:30
parent edec704950
commit df90f8ac01

View file

@ -77,7 +77,7 @@ how to fix possible problems. Another one is:
To see service status with systemd, you can use: To see service status with systemd, you can use:
$ systemctl status gitlab.target $ systemctl status gitlab.service -l
$ systemctl status gitlab-unicorn.service -l $ systemctl status gitlab-unicorn.service -l
$ systemctl status gitlab-sidekiq.service -l $ systemctl status gitlab-sidekiq.service -l
$ systemctl status gitlab-workhorse.service -l $ systemctl status gitlab-workhorse.service -l
@ -98,7 +98,7 @@ Migrating from non-Debian gitlab
2. Install Debian gitlab: 2. Install Debian gitlab:
$ apt-get install gitlab $ apt-get install gitlab
3. Stop gitlab services: 3. Stop gitlab services:
$ systemctl stop gitlab.target $ systemctl stop gitlab.service
4. Rename your old database to gitlab_production and set the user gitlab as 4. Rename your old database to gitlab_production and set the user gitlab as
its owner and the owner of all its tables, sequences and views its owner and the owner of all its tables, sequences and views
$ su - postgres $ su - postgres
@ -125,7 +125,7 @@ Migrating from non-Debian gitlab
# su gitlab # su gitlab
$ /usr/share/gitlab-shell/bin/create-hooks $ /usr/share/gitlab-shell/bin/create-hooks
12. Start gitlab: 12. Start gitlab:
$ systemctl start gitlab.target $ systemctl start gitlab.service
13. Check the installation: 13. Check the installation:
$ runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat /etc/gitlab/gitlab-debian.conf) && rake gitlab:check RAILS_ENV=production' $ runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat /etc/gitlab/gitlab-debian.conf) && rake gitlab:check RAILS_ENV=production'