Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ Then `git push` to heroku as usual.

## NOTES

Meteor apps deployed to Heroku cannot use more than one dyno. Heroku's load balancer does not support sticky sessions.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@doctorpangloss I don't think "cannot use more than one dyno" is correct. The issue you're referring to is that clients who aren't using websockets fall back to http requests (see here), and those may go to a different dyno.

Correct me if I'm wrong, but I believe the only issue with that is that DDP updates may be delayed if they're based on Mongo poll-and-diff. And setting up oplog tailing should take care of most of these situations.

Websockets connections are sticky.

So I think the only issue is that clients that don't support websockets may have delays on only some DDP updates if oplog tailing is not enabled.


You need to set the `ROOT_URL` environment variable:

```bash
Expand All @@ -24,11 +26,10 @@ You can specify meteor settings by setting the `METEOR_SETTINGS` environment var
heroku config:add METEOR_SETTINGS='{"herp":"derp"}'
```


You need to have a verified account so the buildpack can add a `mongohq:sandbox` addon.

## Websockets

To enable websockets on Heroku, you will need to enable the "labs" feature:
Websockets, as of July 7th, are enabled on all new apps deployed on Heroku. For apps deployed before then, run the command:

```heroku labs:enable websockets```