Bind servers to 0.0.0.0 in Procfile

[zunda]

Following #11302 and #11326, this change makes it easier to deploy Mastodon as a Heroku app.

The second line is to be used for a separate app to receive streaming requests.

[Gargron]

Why commented out, and why not call it "streaming"?

[zunda]

Heroku only routes requests from the Internet at ports 80 or 443 to "web" dynos.

To run the streaming server on Heroku, a separate app that shares Postgres and Redis with the main app is needed. On that app, the node process needs to run on "web" dynos.

[Gargron]

Okay. I would format it like this:

web: BIND=0.0.0.0 bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq

# For the streaming API, you need a separate app that shares Postgres and Redis with
# the main one, and runs this dyno:
# web: BIND=0.0.0.0 node ./streaming 

[zunda]

I pushed d7d15d4 so that the admin doesn't have to edit the Procfile. How does this look to you?

[zunda]

Cool. I'll try to come up with more through procedure while keeping it short here.

…

On Sun, Jul 21, 2019, 16:20 Eugen Rochko ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In Procfile <#11378 (comment)>: > @@ -1,2 +1,3 @@ -web: bundle exec puma -C config/puma.rb +web: BIND=0.0.0.0 bundle exec puma -C config/puma.rb +#web: BIND=0.0.0.0 node ./streaming # for streaming app Okay. I would format it like this: web: BIND=0.0.0.0 bundle exec puma -C config/puma.rb worker: bundle exec sidekiq # For the streaming API, you need a separate app that shares Postgres and Redis with # the main one, and runs this dyno: # web: BIND=0.0.0.0 node ./streaming — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11378>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAHR6ELIGT6WEKZAF3OJFTQAUKPRANCNFSM4IFUA4ZQ> .