Skip to content

Commit ef0a495

Browse files
committed
Explain Issues with Multi-Process Servers
Move the details of [#94] to the README. [#94]: #94
1 parent b28353e commit ef0a495

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

+12
Original file line numberDiff line numberDiff line change
@@ -234,6 +234,18 @@ example, `/ember-tests`) and the name of the Ember app.
234234
For example, to view tests of the `frontend` app, visit
235235
`http://localhost:3000/ember-tests/frontend`.
236236

237+
## Serving from multi-process servers in development
238+
239+
If you're using a multi-process server ([Puma], [Unicorn], etc.) in development,
240+
make sure it's configured to run a single worker process.
241+
242+
Without restricting the server to a single process, [it is possible for multiple
243+
EmberCLI runners to clobber each others' work][#94].
244+
245+
[Puma]: https://github.com/puma/puma
246+
[Unicorn]: https://rubygems.org/gems/unicorn
247+
[#94]: https://github.com/thoughtbot/ember-cli-rails/issues/94#issuecomment-77627453
248+
237249
## Enabling LiveReload
238250

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

0 commit comments

Comments
 (0)