Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
c99d5830
Commit
c99d5830
authored
Nov 16, 2017
by
Michael Kozono
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update database_debugging.md
parent
8922b7b7
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
4 deletions
+11
-4
doc/development/database_debugging.md
doc/development/database_debugging.md
+11
-4
No files found.
doc/development/database_debugging.md
View file @
c99d5830
...
...
@@ -9,17 +9,24 @@ An easy first step is to search for your error in Slack or google "GitLab <my er
Available
`RAILS_ENV`
-
`production`
(generally not for your main GDK db, but you may need this for e.g. omnibus)
-
`development`
(this is your main GDK db)
-
`test`
(used for tests like rspec and spinach)
## Nuke everything and start over
If you just want to delete everything and start over
,
If you just want to delete everything and start over
with an empty DB (~1 minute):
-
`bundle exec rake dev:setup RAILS_ENV=development`
: Also runs DB specific stuff and seeds dummy data (slow)
-
`bundle exec rake db:reset RAILS_ENV=development`
: Doesn't do the above (fast)
-
`bundle exec rake db:reset RAILS_ENV=test`
: Fix the test DB, since it doesn't contain important data.
-
`bundle exec rake db:reset RAILS_ENV=development`
If you just want to delete everything and start over with dummy data (~40 minutes). This also does
`db:reset`
and runs DB-specific migrations:
-
`bundle exec rake dev:setup RAILS_ENV=development`
If your test DB is giving you problems, it is safe to nuke it because it doesn't contain important data:
-
`bundle exec rake db:reset RAILS_ENV=test`
## Migration wrangling
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment