however, caching is improvement, serving static files from s3 1) works, but 2) costs money for every serving 3) reveals your bucket name 4) sometimes makes you very dependent on bucket name (for example when you hardcode it on the mobile clients of your rails api)
@gingitsune it's not really rails-only way, but upgrading production in small steps is better (if possible). I usually go with ruby upgrade, then rails upgrade. Between them I wait several hours/days/weeks to find out possible problems.
@Arkentias you won't be able to have several deleted records. If it's ok, maybe it worth trying. But it feels like in this case it's better to have some kind of versioning to keep track of product stock history. Or don't have `deleted_at` on this table at all, if you don't need history.