taco-nginx
Bash script that runs a service and forwards a subdomain to it using nginx when it listens to $PORT
taco-nginx: a subdomain for whatever your service listens on
A bash script that starts your service and points a subdomain at it once the service starts listening on the port in $PORT, so nobody has to hand write nginx configuration per service.
The script does one thing
The whole project is a single behaviour, and the README does not pretend otherwise. taco-nginx runs a service, waits for it to listen on the port stored in $PORT, and then asks nginx to route a subdomain to it. That removes the manual step of editing nginx configuration by hand for each new service, which is the part most people would rather skip. You point the script at your service, give it a subdomain, and the wiring happens on its own. The one sentence description on the project page matches the README exactly, so the scope stays clear from the start.
Which nginx version is expected
The README recommends the latest stable nginx, version 1.8.0. On Ubuntu LTS, for instance, you may need extra steps to get that version installed, because the packaged version can trail behind. The version note is there because the script leans on features the older packages may not carry, and without the right nginx the routing simply will not behave as expected.
How a run looks in practice
A typical run spawns node server.js, waits for it to bind the port from $PORT, and then hands the subdomain over to nginx so requests get forwarded to the running service. The example names the service my-service. It is a small pattern, but it covers a common situation: a local server you want reachable on a subdomain without babysitting the proxy config.
Community notes