New user confusion

[silent-e]

This looks great and I got it installed, started dnsmasq and got the hello.test response. However, as a long time user of puma-dev, I'm confused. One of the giant benefits that I saw of puma-dev was it automatically started the app for me. I didn't have to manually rails s or anything. I could link a new app and it would handle it all. Doesn't look like that's a thing here or with caddy. I saw the bit in the But why? section discussing about how puma-dev doesn't play nice with containerized apps so I understand that part. But for my local dev work I'm not containerizing so it sounds like I'm probably better off staying with puma-dev for the simplicity of things. I can see how if someone is running a local containerized dev setup they'd reverse-proxy to the exposed port of the container. At least I think that's how it'd work.

What you've got here is awesome and simple enough for even a caddy-noob like me to understand and install so I am not at all denigrating the work. Just trying to understand this possible limitation.

Am I getting something wrong here? Thanks.

(e)

[silent-e]

Could we use caddy-dev, proxying to puma-dev like Andre does in this article? Just install puma-dev running on different ports, let caddy handle 80/443 but caddy-dev handles the persistent service we can brew restart to reload config? Sounds more complicated but gives us autoloading of the app, and, if I understand it correctly, the value proposition of caddy-dev in your "But why?" section?

https://andre.arko.net/2023/07/23/caddy-plus-puma-dev-with-ssl/

Actually, that's a "fix it" article. The one you link to at the bottom of your README is the original and explains installing puma-dev on different ports to remove the conflict.