Yorick Peterse a54af831ba 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".		2016-04-14 15:53:54 +02:00
..
ci	Rails update to 4.2.4	2015-11-25 18:18:44 +02:00
background_jobs	Direct sidekiq boot output to log file	2016-01-15 11:12:49 +01:00
bundle
check
daemon_with_pidfile	Properly daemonize the mail_room process	2015-08-27 16:35:00 +02:00
mail_room	Properly daemonize the mail_room process	2015-08-27 16:35:00 +02:00
parallel-rsync-repos	Add 'resume' capability to parallel-rsync-repos	2015-12-08 15:08:22 +01:00
pkgr_before_precompile.sh
rails	Rails update to 4.2.4	2015-11-25 18:18:44 +02:00
rake	Rails update to 4.2.4	2015-11-25 18:18:44 +02:00
rspec	Updated rspec to rspec 3.x syntax	2015-02-12 19:17:35 +01:00
setup	Use rake db:reset instead of db:setup	2016-04-14 15:53:54 +02:00
spinach
spring	Update spring, re-run binstubs	2015-05-20 18:39:33 -04:00
upgrade.rb	Rails update to 4.2.4	2015-11-25 18:18:44 +02:00
web	Improve bin/ launchers	2016-01-14 15:08:15 +01:00