News for hackers. Stuff that matters.
Re:Removed gem breaks Rails ActiveStorage by freedomben on Wednesday March 24, 2021 @11:01AM (#26568084)
After the "left-pad" fiasco, and a similar event on the Ruby side, I started vendoring my dependencies as standard practice. I have not been sorry yet, in fact I feel vindicated in that approach.
Re:Removed gem breaks Rails ActiveStorage by imhoguy on Wednesday March 24, 2021 @11:13AM (#26568244)
Re:Removed gem breaks Rails ActiveStorage by JamesSwift on Wednesday March 24, 2021 @12:10PM (#26569108)
Vendoring in ruby land is a double edged sword. It is much safer as you said. However if you _do_ vendor, be sure to be running containerized first. Otherwise you will be in a very frustrating spot of having to handle all sorts of native gem issues when trying to run on various computers during dev/test/prod.
Re:Removed gem breaks Rails ActiveStorage by freedomben on Wednesday March 24, 2021 @04:59PM (#26572826)
Yes this is a real problem. We primarily use docker which solves the issue, but there are people that hate docker and want to run native. For the mac users that doesn't go too well.
Re:Removed gem breaks Rails ActiveStorage by JamesSwift on Thursday March 25, 2021 @09:04AM (#26579714)
Ive lost countless work days to figuring out gem build issues on mac when everyone else on the team was running on linux/vagrant.
Re:Removed gem breaks Rails ActiveStorage by TomOwens on Wednesday March 24, 2021 @11:03AM (#26568119)
Vendoring is a good first step, too. As long as you have a local copy of all the dependencies, you're better off than needing to go pull them from the Internet every time you want them and risk having them gone. Potentially worse is having the same version but with modifications.
Re:Removed gem breaks Rails ActiveStorage by graywh on Wednesday March 24, 2021 @11:08AM (#26568174)
we get a form of this with our two-stage image building process -- the first stage installs all dependencies and we only update it when dependencies change