Logs are missing / broken after Capistrano deployment

[orenyk]

Discovered while trying to debug #1344, we can't find the application logs on the production server after the new Capistrano deployment. The default log files appear to be empty, we need to figure this out and fix it.

[orenyk]

I initially thought we should maybe remove shared logging but that actually doesn't make sense. I'm trying to debug this on the dev server but am having some issues - will see if ITS can help us out.

[orenyk]

Ok, back to this :-). Let's see what ITS had to say about the subject...

[orenyk]

Figured it out (well, thanks to SO) - looks like its the rails-12factor gem. I'm working on refactoring our Gemfile.

[orenyk]

woot, all done, and tested on DigitalOcean to work correctly. Now to check that it doesn't break Heroku deployment

[orenyk]

Ok, we broke Heroku deployment. Unfortunately Heroku isn't installing the gems in the heroku group by default, and the version of bundler they use (1.9.7) doesn't support the --with flag to specify a Gemfile group to include. I've tried updating our custom heroku buildpack but so far I can't figure out how to update the version of bundler we're using. I think I'm wrapping up for the night but I'll pick this up again soon.