Menu
When we run cap deploy, it runs all the migrations during deployment. We have to point the application to existing DB and don't want modify existing DB.
Can anybody suggest how can we skip the migration step while deploying the application?
538
A Rails migration is a tool for changing an application's database schema. Instead of managing SQL scripts, you define database changes in a domain-specific language (DSL). The code is database-independent, so you can easily move your app to a new platform.
Internally Rails only uses the migration's number (the timestamp) to identify them. Prior to Rails 2.1 the migration number started at 1 and was incremented each time a migration was generated. With multiple developers it was easy for these to clash requiring you to rollback migrations and renumber them.
On databases that support transactions with statements that change the schema, migrations are wrapped in a transaction. If the database does not support this then when a migration fails the parts of it that succeeded will not be rolled back. You will have to rollback the changes that were made by hand.
Capistrano is an open-source tool for running scripts on multiple servers; its main use is deploying web applications.
I suppose you are using capistrano/rails.
According to the doc, you can require just what you need manually:
# Capfile
require 'capistrano/bundler'
require 'capistrano/rails/assets'
# require 'capistrano/rails/migrations'
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
