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
They both amount to packaging up ruby + <app> into an executable. ruby-packer would be my preferred approach as it seems to have broader support for varying ruby versions and native extensions.
On the flip side, running a ruby-packer-built executable doesn't play nicely with much referencing gem information from outside the executable which is a current requirement of the rubygems source. I don't know if traveling-ruby has the same issue, but either way switching to CLI should take care of that.
The text was updated successfully, but these errors were encountered:
Easy distribution != ruby. That said, there are some options available to make it easier to use
licensed
in non-ruby environmentsdocker images
It's not entirely clear what the best usage of this would be, though a base ruby image + licensed already installed might be useful?
ruby-packaged "executable"
The two most promising options I've seen in this space are
They both amount to packaging up ruby +
<app>
into an executable. ruby-packer would be my preferred approach as it seems to have broader support for varying ruby versions and native extensions.On the flip side, running a ruby-packer-built executable doesn't play nicely with much referencing gem information from outside the executable which is a current requirement of the
rubygems
source. I don't know if traveling-ruby has the same issue, but either way switching to CLI should take care of that.The text was updated successfully, but these errors were encountered: