-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve db setup #503
Comments
Which standard rake tasks provide the functionality of the removed rake tasks ? |
|
output from all new tasks: `
** Invoke db:load_config (first_time) ------------------------ api_log_staging schema loading ----------------------------- ------------------------ whois_staging schema loading ----------------------------- ---------------------------- Import seed ---------------------------------------- All done! import@staging:~/registry$ RAILS_ENV=staging rake --trace db:schema:dump:all
** Invoke db:load_config (first_time) ---------------------------- staging schema dump-------------- ---------------------------- api_log_staging ---------------------------------------- ---------------------------- whois_staging ----------------------------------------
** Invoke db:load_config (first_time) ------------------------ api_log_staging schema loading ----------------------------- ------------------------ whois_staging schema loading ----------------------------- |
in master, not yet deployed to production |
OK, all nessecery tables and schemas are created with db:setup:all |
in production |
Remove
db/schema-read-only.rb
and keep usingdb/structure.sql
only. Merging the former requires additional effort with no benefit.Simplify lib/tasks/db.rake and use standard rake tasks as much as possible.
Remove rake tasks:
Introduce new rake tasks (custom):
The text was updated successfully, but these errors were encountered: