Download as
Browse Code »

Commit 031008648f3c2ffb860c39899398dceb395d2948

Authored by Dmitriy Zaporozhets
1 parent 2c8a46e0
Exists in master and in 4 other branches 6-8-stable, 7-0-stable, 7-0-stable-spb, spb-stable

Add RAILS_ENV to rake docs

Showing 3 changed files with 10 additions and 10 deletions   Show diff stats
doc/raketasks/backup_restore.md
  Diff comments   View file @0310086
... ... @@ -4,7 +4,7 @@ Creates a backup archive of the database and all repositories. This archive will
4 4 The filename will be `[TIMESTAMP]_gitlab_backup.tar`. This timestamp can be used to restore an specific backup.
5 5  
6 6 ```
7   -bundle exec rake gitlab:backup:create
  7 +bundle exec rake gitlab:backup:create RAILS_ENV=production
8 8 ```
9 9  
10 10 Example output:
... ... @@ -40,7 +40,7 @@ Deleting old backups... [SKIPPING]
40 40 ### Restore a previously created backup
41 41  
42 42 ```
43   -bundle exec rake gitlab:backup:restore
  43 +bundle exec rake gitlab:backup:restore RAILS_ENV=production
44 44 ```
45 45  
46 46 Options:
... ...
doc/raketasks/features.md
  Diff comments   View file @0310086
... ... @@ -13,7 +13,7 @@ Old path: `git@example.org:myrepo.git`
13 13 New path: `git@example.org:username/myrepo.git` or `git@example.org:groupname/myrepo.git`
14 14  
15 15 ```
16   -bundle exec rake gitlab:enable_namespaces
  16 +bundle exec rake gitlab:enable_namespaces RAILS_ENV=production
17 17 ```
18 18  
19 19  
... ... @@ -22,7 +22,7 @@ bundle exec rake gitlab:enable_namespaces
22 22 This command will enable the auto merge feature. After this you will be able to **merge a merge request** via GitLab and use the **online editor**.
23 23  
24 24 ```
25   -bundle exec rake gitlab:enable_automerge
  25 +bundle exec rake gitlab:enable_automerge RAILS_ENV=production
26 26 ```
27 27  
28 28 Example output:
... ...
doc/raketasks/maintenance.md
  Diff comments   View file @0310086
... ... @@ -7,7 +7,7 @@ Runs the following rake tasks:
7 7 * gitlab:app:enable_automerge (see "Features")
8 8  
9 9 ```
10   -bundle exec rake gitlab:app:setup
  10 +bundle exec rake gitlab:app:setup RAILS_ENV=production
11 11 ```
12 12  
13 13  
... ... @@ -17,7 +17,7 @@ This command gathers information about your GitLab installation and the System
17 17 it runs on. These may be useful when asking for help or reporting issues.
18 18  
19 19 ```
20   -bundle exec rake gitlab:env:info
  20 +bundle exec rake gitlab:env:info RAILS_ENV=production
21 21 ```
22 22  
23 23 Example output:
... ... @@ -68,7 +68,7 @@ It will check that each component was setup according to the installation guide
68 68 You may also have a look at our [Trouble Shooting Guide](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide).
69 69  
70 70 ```
71   -bundle exec rake gitlab:check
  71 +bundle exec rake gitlab:check RAILS_ENV=production
72 72 ```
73 73  
74 74 Example output:
... ... @@ -145,7 +145,7 @@ This will create satellite repos for all your projects.
145 145 If necessary, remove the `tmp/repo_satellites` directory and rerun the command below.
146 146  
147 147 ```
148   -bundle exec rake gitlab:satellites:create
  148 +bundle exec rake gitlab:satellites:create RAILS_ENV=production
149 149 ```
150 150  
151 151  
... ... @@ -154,7 +154,7 @@ bundle exec rake gitlab:satellites:create
154 154 This will send all users ssh public keys to gitolite and grant them access (based on their permission) to their projects.
155 155  
156 156 ```
157   -bundle exec rake gitlab:gitolite:update_keys
  157 +bundle exec rake gitlab:gitolite:update_keys RAILS_ENV=production
158 158 ```
159 159  
160 160  
... ... @@ -163,7 +163,7 @@ bundle exec rake gitlab:gitolite:update_keys
163 163 This makes sure that all projects are present in gitolite and can be accessed.
164 164  
165 165 ```
166   -bundle exec rake gitlab:gitolite:update_repos
  166 +bundle exec rake gitlab:gitolite:update_repos RAILS_ENV=production
167 167 ```
168 168  
169 169 ### Import bare repositories into GitLab project instance
... ...