What does this give me over, for example, Caddy? “Comes set up out of the box” doesn’t really count as setting Caddy up equivalently is probably a matter of sharing a single config file around - not a heavy lift at all.
> Thruster also wraps the Puma process so that you can use it without managing multiple processes yourself. This is particularly useful when running in a containerized environment, where you typically won't have a process manager available to coordinate the processes. Instead you can use Thruster as your CMD, and it will manage Puma for you.
Nothing this does that Caddy can’t do, but Thruster is more the omakase type thing. It’s set up to automatically handle one scenario very well - a single server rails app running defaults. If you have a single server rails app running defaults, this is actually shows up automatically in the automatically generated Dockerfile.
What does this give me over, for example, Caddy? “Comes set up out of the box” doesn’t really count as setting Caddy up equivalently is probably a matter of sharing a single config file around - not a heavy lift at all.
From the project README:
> Thruster also wraps the Puma process so that you can use it without managing multiple processes yourself. This is particularly useful when running in a containerized environment, where you typically won't have a process manager available to coordinate the processes. Instead you can use Thruster as your CMD, and it will manage Puma for you.
Nothing this does that Caddy can’t do, but Thruster is more the omakase type thing. It’s set up to automatically handle one scenario very well - a single server rails app running defaults. If you have a single server rails app running defaults, this is actually shows up automatically in the automatically generated Dockerfile.