Best practice for deploying Rails projects with Thruster

[hooopo]

I read the README and found the descriptions to be very simple, leaving me with some questions. What are the best practices for deploying Rails projects with Thruster, just SSL_DOMAIN=example.com thrust rails server? How do we handle scaling and auto-restart issues, are there any examples to refer to?

[3v0k4]

I know you are awaiting an answer from the maintainers, but I was passing by 🙂

Thruster works best when paired with containers like Docker. Since it wraps Puma, you can use it as the CMD.

If you dockerize your app, you can use any orcherstration tool to take care of scaling and similar concerns.

There's a milestone in the Rails repo set for v8 that covers part of your questions: rails/rails#50479

[hooopo]

@3v0k4 thanks

[jmonteiro]

In the meantime, with Rails 7.1, you can use dockerfile-rails: on your Rails project just bundle add dockerfile-rails and then bin/rails g dockerfile --thruster.

[hooopo]

@jmonteiro cool 🎉

[reesericci]

If you'd like an example for a Dockerfile thruster deployment, I used it in my app United - https://codeberg.org/reesericci/united. There's a custom startup script in bin/, setuid to allow for usage with systemd dynamic users (the install script contains the unit), and a couple changes to the Dockerfile. It also uses my fork of thruster for self-signed TLS.