summaryrefslogtreecommitdiff
path: root/bin/setup
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2016-04-14 15:53:54 +0200
committerYorick Peterse <yorickpeterse@gmail.com>2016-04-14 15:53:54 +0200
commita54af831bae023770bf9b2633cc45ec0d5f5a66a (patch)
tree73a49760298375202530c0cf383a4f304c2894e6 /bin/setup
parentbadb35335086b90e2522ea2da767830f2f3ba9a7 (diff)
downloadgitlab-ce-a54af831bae023770bf9b2633cc45ec0d5f5a66a.tar.gz
Use rake db:reset instead of db:setup
Using db:reset ensures existing tables are first dropped. This in turn ensures that we can drop tables regardless of any foreign key constraints. While CE currently doesn't have any foreign keys EE defines the following relation: remote_mirrors.project_id -> projects.id MySQL will complain whenever you try to drop the "projects" table first even when using "DROP TABLE ... CASCADE".
Diffstat (limited to 'bin/setup')
-rwxr-xr-xbin/setup2
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/setup b/bin/setup
index acdb2c1389c..6cb2d7f1e3a 100755
--- a/bin/setup
+++ b/bin/setup
@@ -18,7 +18,7 @@ Dir.chdir APP_ROOT do
# end
puts "\n== Preparing database =="
- system "bin/rake db:setup"
+ system "bin/rake db:reset"
puts "\n== Removing old logs and tempfiles =="
system "rm -f log/*"