Gemfile's new clothes - Depfu Blog
Jan Krutisch, Co-Founder at Depfu 06 September 2017 The Bundler team currently works hard on pushing Bundler to the 2.0 release. This release will change a lot of default behavior, so it might be good to catch up with these changes way before the actual release. Some of the things that Bundler 2.0 will change are already possible with the latest releases, they’re just not default yet. Probably one
Bundler and private dependencies - Depfu Blog
As soon as you start using private Github repos in your Gemfile you have to figure out how Bundler can access them. This is super easy on your local machine, as Bundler just uses your credentials, so if you can access the repo, so can Bundler. Things get a bit trickier when you want to use a CI service like Travis or when you want to deploy your app to production. Since we needed to support privat
Bundler’s new update options - Depfu Blog
Bundler added new CLI options in the last two releases that allow you to influence how bundle update decides which versions to update to. The new options give you a lot more control than before when updating gems but are also a bit complicated to understand. Let’s have a look: The Goal: Be more conservative The main reason behind all the new options is to allow a more “conservative” approach of up
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Now with more changelog contents - Depfu Blog
How we trick Bundler and cause interesting bugs - Depfu Blog
On Bundler 2.0 compatibility - Depfu Blog
