ruby - is it ok to deploy an older version of your rails app to heroku not doing a rollback? -


if deploy v.15 heroku inside c:/app folder, causing unforeseen issues. can go through typical deploy using git add . git add -u git commit -m "older"etc on older version deploy v.13 backed few days ago?

in v.15 deploy, there new table creation - > heroku rake db:migrate well

i'm trying app working again want cautious

yes. long normal commit in history of repo, should fine. said, better method accomplish you're trying might use git's cherry-pick functionality.

if you're unsure, may wish create second application. can use new heroku fork feature (new of v2.36 of toolbelt - use heroku fork more info it) in order clone app new app. great way creating staging environment existing app.

you use see how deploying new (old?) changes work. hope helps!


Comments

Popular posts from this blog

android - getbluetoothservice() called with no bluetoothmanagercallback -

sql - ASP.NET SqlDataSource, like on SelectCommand -

ios - Undefined symbols for architecture armv7: "_OBJC_CLASS_$_SSZipArchive" -