Closed Gionni closed 9 years ago
Hi,
I can't make it work. Seems my node.js app (port 3000) is called in spite of nginx (port 3001).
1. $ heroku config:set BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git $ echo 'https://github.com/heroku/heroku-buildpack-nodejs.git' >> .buildpacks $ echo 'https://github.com/Gionni/nginx-buildpack.git' >> .buildpacks [minimal fork ryandotsmith] 2. Procfile: web: bin/start-nginx ./node_modules/.bin/forever app.js 3. $ git add... / commit... / push heroku... All goes ok but nginx.conf, even if executed, seems to have no effects. My app pops out, anyway.
http { server { listen <%= ENV["NGINX_PORT"] %>; location / { proxy_pass http://www.nytimes.com/; } } }
Any suggestion for making nginx king rather than what should be hidden? Thanks, Johnny
Solved. Gotta pay attention to Heroku PORT.
Hi,
I can't make it work. Seems my node.js app (port 3000) is called in spite of nginx (port 3001).
1. $ heroku config:set BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git $ echo 'https://github.com/heroku/heroku-buildpack-nodejs.git' >> .buildpacks $ echo 'https://github.com/Gionni/nginx-buildpack.git' >> .buildpacks [minimal fork ryandotsmith] 2. Procfile: web: bin/start-nginx ./node_modules/.bin/forever app.js 3. $ git add... / commit... / push heroku... All goes ok but nginx.conf, even if executed, seems to have no effects. My app pops out, anyway.
http { server { listen <%= ENV["NGINX_PORT"] %>; location / { proxy_pass http://www.nytimes.com/; } } }
Any suggestion for making nginx king rather than what should be hidden? Thanks, Johnny