summaryrefslogtreecommitdiff
path: root/doc/development/rake_tasks.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-02-08 03:08:47 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-02-08 03:08:47 +0000
commit91ed938e3d17d385a08459915972d7e3f6b8468e (patch)
tree194203988e612d82afbcc20f9aaf06ab6a451b39 /doc/development/rake_tasks.md
parentbef1bd93d113723a156f5943e743193afad1ef71 (diff)
downloadgitlab-ce-91ed938e3d17d385a08459915972d7e3f6b8468e.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/rake_tasks.md')
-rw-r--r--doc/development/rake_tasks.md22
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/development/rake_tasks.md b/doc/development/rake_tasks.md
index d9b2ace1b5b..83dd5027a02 100644
--- a/doc/development/rake_tasks.md
+++ b/doc/development/rake_tasks.md
@@ -4,7 +4,7 @@
Note that if your db user does not have advanced privileges you must create the db manually before running this command.
-```
+```shell
bundle exec rake setup
```
@@ -70,7 +70,7 @@ Group are additionally seeded with epics if GitLab instance has epics feature av
If you're very sure that you want to **wipe the current database** and refill
seeds, you could:
-``` shell
+```shell
echo 'yes' | bundle exec rake setup
```
@@ -83,7 +83,7 @@ your terminal, and it would generate more than 20G logs if you just redirect
it to a file. If we don't care about the output, we could just redirect it to
`/dev/null`:
-``` shell
+```shell
echo 'yes' | bundle exec rake setup > /dev/null
```
@@ -138,13 +138,13 @@ you don't need to boot it every time you run a test, rake task or migration.
If you want to use it, you'll need to export the `ENABLE_SPRING` environment
variable to `1`:
-```
+```shell
export ENABLE_SPRING=1
```
Alternatively you can use the following on each spec run,
-```
+```shell
bundle exec spring rspec some_spec.rb
```
@@ -154,7 +154,7 @@ You shouldn't ever need to compile frontend assets manually in development, but
if you ever need to test how the assets get compiled in a production
environment you can do so with the following command:
-```
+```shell
RAILS_ENV=production NODE_ENV=production bundle exec rake gitlab:assets:compile
```
@@ -167,7 +167,7 @@ they can be easily inspected.
To update the Emoji aliases file (used for Emoji autocomplete) you must run the
following:
-```
+```shell
bundle exec rake gemojione:aliases
```
@@ -176,7 +176,7 @@ bundle exec rake gemojione:aliases
To update the Emoji digests file (used for Emoji autocomplete) you must run the
following:
-```
+```shell
bundle exec rake gemojione:digests
```
@@ -187,7 +187,7 @@ available Emoji.
Generating a sprite file containing all the Emoji can be done by running:
-```
+```shell
bundle exec rake gemojione:sprite
```
@@ -201,7 +201,7 @@ task, then check the dimensions of the new spritesheet and update the
Starting a project from a template needs this project to be exported. On a
up to date master branch run:
-```
+```shell
gdk start
bundle exec rake gitlab:update_project_templates
git checkout -b update-project-templates
@@ -233,7 +233,7 @@ a file for quick reference.
To see a list of all obsolete `ignored_columns` run:
-```
+```shell
bundle exec rake db:obsolete_ignored_columns
```