Thank you, I did run the cap deploy:migrate
task. But here the problem was that I was validating the existence of a newly created field and this caused the trouble with the records which where already in the database.
thanks.
Question
I have a Rails 3.2 application and I have some issues on the production side:
I have a model 'Poject' and did a migration to add a string for 'description'.
running
rake db:migrate
works fine on my developer machine like all the times.
But when I do a cap deploy
and cap migrate
on the production server I cannot update my
project models which where already in the database. Only new ones work fine.
I'm using postgres 9.1
I don't know what's the issue here since its working fine on my local machine.
Regards
Oliver
Solution 2
Thank you, I did run the cap deploy:migrate
task. But here the problem was that I was validating the existence of a newly created field and this caused the trouble with the records which where already in the database.
thanks.
OTHER TIPS
I think what you are looking for is cap deploy:migrate
.
Run the migrate rake task. By default, it runs this in most recently deployed
version of the app...
You can read more about it here: https://github.com/capistrano/capistrano/wiki/Capistrano-Tasks
Also make sure you are using the right environment while using capistrano