BigW Consortium Gitlab

Skip to content

G
gitlab-ce
Commit 83e9825c by Jacob Vosmaer
Options

Fix sudo commands in update guides

parent b658489f
Showing with 11 additions and 11 deletions
doc/update/5.1-to-5.2.md
......@@ -7,7 +7,7 @@ It's useful to make a backup just in case things go south:
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
......@@ -95,5 +95,5 @@ Follow the [`upgrade guide from 5.0 to 5.1`](5.0-to-5.1.md), except for the data
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:restore
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
doc/update/5.2-to-5.3.md
......@@ -7,7 +7,7 @@ It's useful to make a backup just in case things go south:
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
......@@ -78,5 +78,5 @@ Follow the [`upgrade guide from 5.1 to 5.2`](5.1-to-5.2.md), except for the data
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:restore
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
doc/update/5.3-to-5.4.md
......@@ -7,7 +7,7 @@ It's useful to make a backup just in case things go south:
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
......@@ -86,5 +86,5 @@ Follow the [`upgrade guide from 5.2 to 5.3`](5.2-to-5.3.md), except for the data
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:restore
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
doc/update/5.4-to-6.0.md
......@@ -24,7 +24,7 @@ It's useful to make a backup just in case things go south:
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
......
doc/update/6.0-to-6.1.md
......@@ -16,7 +16,7 @@ It's useful to make a backup just in case things go south:
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
......@@ -99,5 +99,5 @@ Follow the [`upgrade guide from 5.4 to 6.0`](5.4-to-6.0.md), except for the data
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:restore
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
doc/update/6.1-to-6.2.md
......@@ -9,7 +9,7 @@ It's useful to make a backup just in case things go south:
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
......@@ -96,5 +96,5 @@ Follow the [`upgrade guide from 6.0 to 6.1`](6.0-to-6.1.md), except for the data
```bash
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:restore
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment