With ActionController::Live and Server-Sent Events (in combination with Redis) we were hoping to have found a good solution with not too much overhead. Maybe some of you know that for this to work you can’t go with the WebRICK web server - but we were fine to go with Puma.
But what really bugs me: You need to set “config.cache_classes” and “config.eager_load” to “true” for your development environment to let this combination (mentioned above) work out. That means that in development you have to restart the web server (Puma) each time you want code changes to be applied.
Did anyone else encounter these uncomfortable workflow? Is anybody out there who can give me some point to think forward from to find a solution for this?
Right now we’re thinking of a (very, very, very) bad hack: Activate the old-style polling based on JS within development environment to somehow verify that message notifications are send without a page reload and don’t use the ActionController::Live - and go with the good solution in the production environment.
In my opinion I would rather go with a better solution for development …
I would really appreciate any input on this topic