/explore
|
You are here 
|
bundler.io | ||
| | | | |
eregon.me
|
|
| | | | | Bundler 2 did not arrive quietly. It was noticed by almost every CI build failing when running bundle install. As a result, it seems many still avoid Bundler 2 and just use Bundler 1. In this post, I present some ideas on how to get more people to use Bundler 2, and no longer need Bundler 1 which will not be maintained forever. | |
| | | | |
github.com
|
|
| | | | | Lists repositories using end-of-life Ruby versions - MatheusRich/end_of_life | |
| | | | |
mensfeld.pl
|
|
| | | | | Learn how Bundler 2.6's checksum verification protects your Ruby projects from supply chain attacks. Discover implementation steps and best practices for securing your gem dependencies. | |
| | | | |
mfbmina.dev
|
|
| | | Hey guys, editing the post to say that after talking to some people, I noticed that I whole misunderstood how Go dependencies work, and I was expecting some feature that already kind of exists, since just what is used from the code is at the final binary! A special thanks to Laurent Demailly, from Gophers Slack, and to some Reddit users! After many years working with Ruby, I migrate to Go without much experience with the language. My first friction was with dependency management because I always find it bad, with fuzzy commands and, the worst, without distinction between development and production dependencies, since both of them are included in the binary. Let's take a look at a go.mod from a PoC: | ||
