Thank you for this! It is great to finally have a proper real-world example for ActionCable

 ☒ Here's another cool use case for ActionCable too. https://www.driftingruby.com/episodes/realtime-client-updates-from-background-jobs-with-stimulus

☒

Thanks for this. I was thinking how you could have 'somethings' that when included on a page of html could register itself to a channel :)

 ☒ Yea, from nearly every article I've read, this is one of the most common "overlooked" things. StimulusJS may be overkill for this kind of functionality, but it make it so easy to create "situational" websocket subscriptions based on which page you're on by simply adding in the controller name. Disconnecting from a subscription also seems to be a very overlooked topic.

Is this using Rails5 or Rails6?

 ☒ it's using Rails 6. however, you should be able to do the same in Rails 5 with little to no changes. Some of the folder structuring may be different if you've not moved the javascript assets out of sprokets. However, the concepts are the same.

thank you for this tutorial!! how would this work in production? would anything need to be changed?

 ☒ There shouldn't be anything different. However, you would need to set up a Redis instance and connect it to ActionCable in the cable.yml config. 

 ☒ - I can't seem to get the render partial to work. It keeps telling me that there is a missing partial. Could you give me another example on how the partial should be called and what should be added to the view? 

If you're app is using hotwire, I'd definitely recommend that route instead of creating custom channels. It's much cleaner now-a-days and it seems to be more stable and easier to debug.

 ☒ - I'm on Rails 6 without hotwire.