Traveling Ruby VS CodeClimate

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.

Resource Link: CodeClimate

Want to know how to enforce allowing only high-quality software into production? Check out this post on how to use CodeClimate can help you do just that! #DevOps #SoftwareDeveloper #softwaredevelopment #SoftwareEngineering #webdevelopment #codequality

Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes into master, the code is pushed directly to the public environment. Deployment also occurs when a push is made to a development branch enabling local/e2e testing before push to master. In this manner the master branch can be kept clean and ready for deployment most of the time. Problems that surface resulting from changes are visible before reaching master. Additional automated tools are used. Docker images are built for each microservice on commit to a development or master branch, a static code analysis is performed by SonarCloud revealing quality and security problems, Snyk provides vulnerability analysis and CodeClimate provides feedback on code quality while Coveralls provides test coverage. Finally, a CircleCI build is done. Each of these components use badges which give a heads-up display of the health of the system being developed. Incorporating each of these tools into the development process will keep the code on a trajectory of stability. For example, eliminating code smells, security vulnerabilities, and broken tests before merging a pull-request (PR) into master. Using Husky on development machines to ensure that code is well linted and locally tested before it is allowed to be pushed to source-control management (SCM). Applying additional processes such as writing tests around bugs meaning reintroduction of a given bug would cause a test to fail. The automated tools would then require that test to be fixed before push to SCM meaning fewer bugs will be reintroduced. Proper development processes and automation have a strong synergy.

The new code should not drop existing code coverage I've found in practice mainly catches changes to existing code that lack proper updates to existing tests. Our company uses Code Climate for these checks, so we don't have to manage / write our own tooling for this purpose.

Code Climate

Some exciting NYC companies tech companies I like are alloy.co, hyperscience.com, vanta.com, and codeclimate.com.

Best code quality - Thanks to SaaS such as CodeClimate I can tell when my code quality is too low. I try to keep "code smells" absolute zero.

Maintainable with smaller methods, less complexity – To know more on this make a habit of using code analyzer like rubocop, Code Climate