You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This discussion pertains to the article on the Evil Martians blog entitled "Kubing Rails: stressless Kubernetes deployments with Kuby". It is part of a series of discussions pertaining to the article that will hopefully help improve Kuby and its ecosystem.
From the article:
kuby-core depends on the helm-rb and kubectl-rb gems, which contain their corresponding binaries in the distributions. This is a pattern I wish didn’t exist in the Ruby community, but, alas.
Why? As I see it, distributing the binaries as rubygems has the following major benefits:
Bundler chooses the right platform for you, meaning there's no need to guess the platform and download anything at runtime.
No need to install these tools, they're downloaded and installed along with everything else when you run bundle install.
kuby-core can depend on specific versions of the helm-rb and kubectl-rb gems instead of relying on the developer installing the right versions.
The gem can be versioned independently of the tool itself.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This discussion pertains to the article on the Evil Martians blog entitled "Kubing Rails: stressless Kubernetes deployments with Kuby". It is part of a series of discussions pertaining to the article that will hopefully help improve Kuby and its ecosystem.
From the article:
Why? As I see it, distributing the binaries as rubygems has the following major benefits:
bundle install
./cc @palkan
Beta Was this translation helpful? Give feedback.
All reactions