Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage on Heroku #16

Open
kmcq opened this issue Aug 10, 2018 · 2 comments
Open

Usage on Heroku #16

kmcq opened this issue Aug 10, 2018 · 2 comments

Comments

@kmcq
Copy link

kmcq commented Aug 10, 2018

Hello! Thanks so much for writing this gem.

The examples mention localhost and following them I got this set up for my local dev environment quite easily. However, I'm not sure what to use a config for when I've deployed the app (we're using Heroku). I'd be happy to write up and make a PR for the README for how to do this if you could point me in the right direction.

Thanks!

@morochena
Copy link

I'd be interested in this as well.

@bjeanes
Copy link

bjeanes commented Dec 17, 2018

To get this working on Heroku, we'd need to be able to dynamically specify the port that the proxy runs on, as Heroku provides the PORT environment variable that it expects your application to service requests on.

The actual server (e.g. Puma) port could be derived from that, static, or random, but we'd need to be able to reliably tell the proxy what port it is on.

I think, ideally, you'd bind the server to a unix socket and have the communication between the proxy and the application server be via that socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants