Menu
Show activity on this post. It's basically a safety switch, at the expense of complicating and changing how Rails apps are deployed: Rails 5 has added a new table ar_internal_metadata to store environment version which is used at the time of migrating the database.
rails db:reset:primary Drops and recreates the primary database from its schema for the current environment and loads the seeds. rails db:reset:secondary Drops and recreates the secondary database from its schema for the current environment and loads the seeds.
I'm wondering if I need to create a migration for creating ar_internal_metadata in production on Rails 5
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With