Follow along as our friends at Phusion walk us through the process of creating a GitHub Actions workflow to build and publish a Ruby gem to the RubyGems registry.

One of the actions featured in the version that’s currently exclusively available to GitHub employees and a selected and undisclosed group of Beta testers, is the ‘GitHub Action for npm’, which wraps the npm CLI to enable common npm commands.

We set out to instead make an example workflow to build and publish a Ruby library (or: gem) to the default public registry, and created a GitHub repository, with a Docker container for a ‘Rubygems’ action: github.com/scarhand/actions-ruby

Hongli Lai:

A million apps isn’t cool. You know what is cool? A billion apps! Per overwhelming request from language communities Passenger didn’t previously cater to, we introduce generic language support in Passenger 6. Launching in 3, 2, 1…

Passenger began as a Ruby application server, eventually adding support for Node.js, Python, and Meteor apps. Congrats to the relentless team at Phusion for bringing their much-beloved server to even more developer runtimes!

Floor Drees:

Yesterday I attended a Craftwork Amsterdam workshop with the promise to ‘create a GitHub App’. With the help of ‘Hubbers’ Don, Bas and Anisha we built a bot that triages GitHub issues.

It’s always fun to read how folks pull together different tools/services to scratch an itch (or just have some fun).

Floor Drees:

6 maintainers of high profile Ruby projects share their thoughts on maintaining and contributing to open source software with ROSS conf Amsterdam. We transcribed the bestest bits from the video interviews.

Learn from Katrina Owen of Exercism, Michal Papis of RVM, Hongli Lai of Passenger, and more.

The Phusion team open sourced their customer support product –Support Central– which pulls in support requests from different channels, including GitHub Issues.

GitHub tagging through Support Central allows our bootstrapped team to get a quick overview of which tickets are potentially blocked, rather than us periodically scrolling through the list and re-reading all the tickets.

Perhaps your team will find it as useful as they do.

Do you wish you weren’t the only person slaving away on your open source project? Find out how to make your project pull request ready in this guide from our friends at Phusion.

Floor Drees, writes on the Phusion blog:

Newcomers to your project will turn to your issue tracker and look at (merged) pull requests, discussion forums, mailing lists or chat channels to form an idea of what your project is like and how and where they can best contribute. Optimizing these channels for on-boarding contributors will set you up for success.

Hongli Lai, co-founder of Phusion and Passenger engineer, shares his quest for an easy-to-use monitoring solution for Phusion’s servers.

Unlike the other solutions I’ve checked out, Netdata provides real-time, per-second monitoring. You can see the CPU/memory slider update in real time. Netdata also provides alerting and installs a ton of alerts by default. By default Netdata stores collected stats on the same server. This is very convenient if you are just getting started. It can also be configured to send stats to a central server.

Also, go back in time to 2015 when we talked with Hongli on The Changelog #136.