deac/gitlabhq
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Add RAILS_ENV to rake docs

Browse source
This commit is contained in:
Dmitriy Zaporozhets 2013-01-05 23:36:04 +02:00
parent 2c8a46e0fe
commit 031008648f
3 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/raketasks/backup_restore.md
View file

@ -4,7 +4,7 @@ Creates a backup archive of the database and all repositories. This archive will
The filename will be `[TIMESTAMP]_gitlab_backup.tar`. This timestamp can be used to restore an specific backup.
```
bundle exec rake gitlab:backup:create
bundle exec rake gitlab:backup:create RAILS_ENV=production
```
Example output:
@ -40,7 +40,7 @@ Deleting old backups... [SKIPPING]
### Restore a previously created backup
```
bundle exec rake gitlab:backup:restore
bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
Options:

4
doc/raketasks/features.md
View file

@ -13,7 +13,7 @@ Old path: `git@example.org:myrepo.git`
New path: `git@example.org:username/myrepo.git` or `git@example.org:groupname/myrepo.git`
```
bundle exec rake gitlab:enable_namespaces
bundle exec rake gitlab:enable_namespaces RAILS_ENV=production
```
@ -22,7 +22,7 @@ bundle exec rake gitlab:enable_namespaces
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**.
```
bundle exec rake gitlab:enable_automerge
bundle exec rake gitlab:enable_automerge RAILS_ENV=production
```
Example output:

12
doc/raketasks/maintenance.md
View file

@ -7,7 +7,7 @@ Runs the following rake tasks:
* gitlab:app:enable_automerge (see "Features")
```
bundle exec rake gitlab:app:setup
bundle exec rake gitlab:app:setup RAILS_ENV=production
```
@ -17,7 +17,7 @@ This command gathers information about your GitLab installation and the System
it runs on. These may be useful when asking for help or reporting issues.
```
bundle exec rake gitlab:env:info
bundle exec rake gitlab:env:info RAILS_ENV=production
```
Example output:
@ -68,7 +68,7 @@ It will check that each component was setup according to the installation guide
You may also have a look at our [Trouble Shooting Guide](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide).
```
bundle exec rake gitlab:check
bundle exec rake gitlab:check RAILS_ENV=production
```
Example output:
@ -145,7 +145,7 @@ This will create satellite repos for all your projects.
If necessary, remove the `tmp/repo_satellites` directory and rerun the command below.
```
bundle exec rake gitlab:satellites:create
bundle exec rake gitlab:satellites:create RAILS_ENV=production
```
@ -154,7 +154,7 @@ bundle exec rake gitlab:satellites:create
This will send all users ssh public keys to gitolite and grant them access (based on their permission) to their projects.
```
bundle exec rake gitlab:gitolite:update_keys
bundle exec rake gitlab:gitolite:update_keys RAILS_ENV=production
```
@ -163,7 +163,7 @@ bundle exec rake gitlab:gitolite:update_keys
This makes sure that all projects are present in gitolite and can be accessed.
```
bundle exec rake gitlab:gitolite:update_repos
bundle exec rake gitlab:gitolite:update_repos RAILS_ENV=production
```
### Import bare repositories into GitLab project instance