Skip to content

Commit

Permalink
Explain Issues with Multi-Process Servers
Browse files Browse the repository at this point in the history
Move the details of [#94] to the README.

[#94]: #94
  • Loading branch information
seanpdoyle committed Oct 21, 2015
1 parent b28353e commit b35ce51
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -234,6 +234,18 @@ example, `/ember-tests`) and the name of the Ember app.
For example, to view tests of the `frontend` app, visit
`http://localhost:3000/ember-tests/frontend`.

## Serving from multi-process servers in development

If you're using a multi-process server ([Puma], [Unicorn], etc.) in development,
make sure it's configured to run a single worker process.

Without restricting the server to a single process, [it is possible for multiple
EmberCLI runners to clobber each others' work][#94].

[Puma]: https://github.com/puma/puma
[Unicorn]: https://rubygems.org/gems/unicorn/versions/4.9.0
[#94]: https://github.com/thoughtbot/ember-cli-rails/issues/94#issuecomment-77627453

## Enabling LiveReload

In order to get LiveReload up and running with Ember CLI Rails, you can install
Expand Down

0 comments on commit b35ce51

Please sign in to comment.