Traveling Ruby VS backports

If you absolutely need a native binary distribution for your apps, there is a project called Traveling Ruby that originated at Phusion, makers of the popular Phusion Passenger Ruby application server. It's worth noting that this project has a number of open issues that are aging and the latest commits are from 2021, so I'm not sure about its current status. There are also important caveats with regard to native extensions and Windows. Given the popularity of packages that require native extensions (like the XML/HTML library Nokogiri), you may find that this solution simply doesn't work for you.

You may be to get a precompiled binary with OpenSSL 1.1 statically linked. Maybe Traveling Ruby? https://github.com/phusion/traveling-ruby

There's really not much else in this space. The main alternative - Traveling Ruby - has limitations on Windows and I don't think it supports Ruby 3.0.

But even with all of the above, you're absolutely right, it is just easier to ship a binary blob. That's where the rewrite totally pays off. I just wonder whether the team has stressed all the options when it comes to keep ruby. There are packaging solutions which ship with its own interpreter, such as Travelling Ruby. And mruby could also generate a binary blob, although they'd have to open another can of works, such as finding replacements for dependencies such as net-ssh, which AFAIK can't be used with mruby. So in the end, maybe they did. And given the prevalence of go products in hashicorp, maybe it makes sense to just invest a bit more in it?

You could try using Traveling Ruby as an alternative to Ocra. I have only used Ocra in the past for this task, but I'd say it's worth a try.

This week we’re talking to Marc-André Lafortune, a longtime contributor to the Ruby and Elixir communities, member of the Ruby and rubocop core teams including the core rubocop-ast engine, and creator of the backports gem.

Yes, I was planning to add it to https://github.com/marcandre/backports, but I didn't have time to. I joined the army training and will be... let's say probably less active in the community for some time.

You might be better off using Ruby 2.x for now and waiting until Ruby 3.0 is supported on either. Are there Ruby 3-specific features you need? There might be support for them via the backports gem.