realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

update README.Debian

Browse source
This commit is contained in:
Praveen Arimbrathodiyil 2016-03-16 19:51:43 +05:30
parent a00d81b6ce
commit dfa945f163
1 changed files with 5 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
debian/README.Debian vendored
View file

@ -48,13 +48,13 @@ Upstream documentation will instruct to run commands like the following:
$ sudo -u gitlab -H bundle exec rake XXX RAILS_ENV=production $ sudo -u gitlab -H bundle exec rake XXX RAILS_ENV=production
Where is something like "db:migrate", "gitlab:check" or "gitlab:env:info". In Where is something like "db:migrate", "gitlab:check" or "gitlab:env:info". In
Debian, the rake command has to be called by the gitlab user from its home Debian, the rake command has to be called by the gitlab user from app home
directory /usr/share/gitlab and with the environment variables from directory /usr/share/gitlab and with the environment variables from
/etc/gitlab/gitlab-debian.conf set. So above command could be run like: /etc/gitlab/gitlab-debian.conf set. So above command could be run like:
# su gitlab # su gitlab
$ cd /usr/share/gitlab $ cd /usr/share/gitlab
$ export $(cat /etc/gitlab/gitlab-debian.conf | xargs) $ export $(cat /etc/gitlab/gitlab-debian.conf)
$ rake XXX RAILS_ENV=production $ rake XXX RAILS_ENV=production
One useful command to run in this environment is: One useful command to run in this environment is:
@ -87,10 +87,8 @@ Migrating from non-Debian gitlab
1. Rename your old database to gitlab_production and set the user gitlab as 1. 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
2. Copy your old repository directory to /var/lib/gitlab/repositories/ 2. Copy your old repository directory to /var/lib/gitlab/repositories/
3. Copy your old public/uploads/ directory to /usr/share/gitlab/public/uploads/ 3. Copy your old public/uploads/ directory to /var/lib/gitlab/public/uploads/
4. Copy your old .ssh/authorized_keys to /usr/share/gitlab/.ssh/authorized_keys 4. Copy your old .ssh/authorized_keys to /var/lib/gitlab/.ssh/authorized_keys
and change the paths to gitlab-shell in your new copy of
.ssh/authorized_keys to /usr/share/gitlab-shell/bin/gitlab-shell
5. Start gitlab using `systemctl start gitlab.target` 5. Start gitlab using `systemctl start gitlab.target`
6. Check the status of your installation using gitlab:check (see section 6. Check the status of your installation using gitlab:check (see section
above). The output of that command will tell you the necessary remaining above). The output of that command will tell you the necessary remaining
@ -107,7 +105,7 @@ Resetting admin password without web interface
# su gitlab # su gitlab
$ cd /usr/share/gitlab $ cd /usr/share/gitlab
$ export $(cat /etc/gitlab/gitlab-debian.conf | xargs) $ export $(cat /etc/gitlab/gitlab-debian.conf)
$ rails console production $ rails console production
irb(main):001:0> user = User.where(admin: true).first irb(main):001:0> user = User.where(admin: true).first
irb(main):002:0> user.password = 'secret_pass' irb(main):002:0> user.password = 'secret_pass'