From b35ce513bb99e51bded3817aa92d1a59701d8cd2 Mon Sep 17 00:00:00 2001 From: Sean Doyle Date: Wed, 21 Oct 2015 14:17:43 -0400 Subject: [PATCH] Explain Issues with Multi-Process Servers Move the details of [#94] to the README. [#94]: https://github.com/thoughtbot/ember-cli-rails/issues/94 --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 7b94e770..663b6c1f 100644 --- a/README.md +++ b/README.md @@ -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