diff options
| author | David Heinemeier Hansson <david@loudthinking.com> | 2015-07-11 11:10:27 +0200 |
|---|---|---|
| committer | David Heinemeier Hansson <david@loudthinking.com> | 2015-07-11 11:10:27 +0200 |
| commit | 763d499d9e7e5502c945e3bacfb02f573e9c2fdd (patch) | |
| tree | 991fc0dabec7a8335675fc76166219be297453e5 | |
| parent | 7f9c8eec2f1f79a97e054c8dcb5353e52c932508 (diff) | |
| download | rails-763d499d9e7e5502c945e3bacfb02f573e9c2fdd.tar.gz rails-763d499d9e7e5502c945e3bacfb02f573e9c2fdd.tar.bz2 rails-763d499d9e7e5502c945e3bacfb02f573e9c2fdd.zip | |
Note that there is no auto-reloading of classes in the cable server
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -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. |