Allow multiple copies of the same app to run independently with different configurations about puma-dev HOT 2 OPEN

I think subdomains solve your problem. You can do

puma-dev link -n api.myapp
puma-dev link -n admin_dashboard.myapp

And then somewhere in an initializer use the subdomain to set the ENV (or equivalent best practice)

from puma-dev.

I'm afraid that didn't work in my testing 😞 My initial experiments above suggested that the .sock file on disk might be the culprit:

• When api.myapp.test boots up (assuming it's the first to boot), it creates a .sock file
• When admin_dashboard.myapp.test boots up a moment later, I believe it finds that .sock file and thus connects to the same already-running Puma instance, rather than spawning a new Puma instance with different ENV vars
• The result is that you're unable to run 2 Puma instances of the same repo side-by-side with different ENV vars

from puma-dev.