Closed kgathi2 closed 9 years ago
After racking my brains, it turns out that my suspicions were right, but not figaro's fault. It was acting like that because i had the following variable in my application.yml
VERSION: '0.0.1'
Cost me my entire staging db!!!!!
There's no telling what ENV variable collisions there could be so I err on the side of explicit rather than generic variable names. Glad you found the cause!
I added figaro to my project and all worked well until i tried doing a
rake db:drop db:create db:migrate
The first two were successful but
rake db:migrate
wont work. If a comment out figaro in the gem file, it works.At one point when i migrated my db, it reversed all the migrations to Version=0. I think this is related as well.