2 ms·
>> I don't pin any of my gems and every time I upgrade Ruby I upgrade the latest version of all the gems too. How do you deal with this in production? Gems ge
by bluedino 9y ago
>> I don't pin any of my gems and every time I upgrade Ruby I upgrade the latest version of all the gems too.
How do you deal with this in production? Gems get abandoned. Some gems get upgraded faster than others. Some before you're ready.
You get into a race where you either need to fix your code, or fix a gem, or not upgrade. What do you do then? What if you don't have time to fix code to deal with a gem upgrade that ca happen at any time?
- 3pt14159 9y agoWhat do you do when a zero day comes out for nginx or openssl? When things somehow go sideways I do the same thing: Triage the situation, including taking things offline if needed, make choices that solve the short term situation, run the tests, everything ok push live. Otherwise mitigate the issue by partially removing services (no image upload right now) and getting the rest of them live. On the server itself I have a second copy of the repo. I install the new version of ruby in that repo and install the gems in that repo. I run the tests there and I check to make sure that Gemfile.lock hasn't changed. All good? Time to go live. Otherwise? Fix things locally first and re-push.