From 763d499d9e7e5502c945e3bacfb02f573e9c2fdd Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Sat, 11 Jul 2015 11:10:27 +0200 Subject: [PATCH] Note that there is no auto-reloading of classes in the cable server --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 15d4611c67..d0acd832c9 100644 --- a/README.md +++ b/README.md @@ -270,6 +270,8 @@ bundle exec puma -p 28080 cable/config.ru That'll start a cable server on port 28080. Remember to point your client-side setup against that using something like: `App.cable.createConsumer('ws://basecamp.dev:28080')`. +Beware that currently the cable server will _not_ auto-reload any changes in the framework. As we've discussed, long-running cable connections mean long-running objects. We don't yet have a way of reloading the classes of those objects in a safe manner. So when you change your channels, or the model your channels use, you must restart the cable server. + Note: We'll get all this abstracted properly when the framework is integrated into Rails. -- GitLab