Roda VS Puppet

Roda (roda.jeremyevans.net)

Jeremy also maintains an awesome web framework called Roda. It's lightweight, fast, and easy to use when you don't need the heft of Rails.

I've been on the Roda [0] and Sequel [1] framework for over 10 years now across various projects. Even after all these years, starting a project in this stack feels like a breath of fresh air even compared to the newer language/frameworks that jabe come out since.

Jeremy Evans is the creator and maintainer of both of these Ruby gems and is super helpful in resolving ask kinda of issues.

[0]: https://roda.jeremyevans.net/

[1]: https://sequel.jeremyevans.net/

My memory is failing me on the specifics, but I posted this issue on roda, which then led to this other issue in omniauth, plus 2 MRs on omniauth and rack-protection for doc updates.

You could pick up a framework like Phoenix, or Remix (the newest kid on the block) and I'm sure you'd get plenty far with either - and if you want ruby, try Roda. You might not have ready made tools with the newer frameworks, so watch out for that. But they have the advantage of doing thing slightly differently.

Even though Rodauth is built on top of Roda and Sequel, it can work as a Rack middleware in any Ruby web framework. In the beginning, there was a demo app showing how Rodauth can be used in Rails, which leveraged the (now discontinued) roda-rails gem. However, the integration felt fairly raw, and definitely lacked the ergonomics Rails developers are used to.

I'm a big fan of Sinatra, but recently I came across Roda which is by Jeremy Evan's whose wonderful ORM gem Sequel I've used in several projects. Looking at the documentation, Roda seems quite nice and performance gain is always appreciated.

For anything but a large app, Roda is well worth considering. It's not the easiest for beginners, due to its philosophy of being bare-bones by default but highly extendable. But it's gradually becoming integrated into Bridgetown, whose batteries-included approach is making Roda much more accessible.

The Puppet 8 compatibility guide detailed the major changes we had to be aware of and we found it invaluable the effort. It's probably worth bookmarking that page until you're done with the upgrade.

I will happily direct your attention here: https://github.com/puppetlabs/puppet

We started by decoupling Puppet from Facter as much as we could, introducing the possibility of having multiple Facter backends. While Puppet would use the default Facter implementation when running on its own, external users would be able to define and pass their own Facter implementation when initializing Puppet, similar to how puppetserver configures Puppet to use its JRuby-compliant HTTP client.