Starting Point
I’m using Hatchbox on a Digital Ocean droplet. When I created the application, Redis was added automatically, which set up the REDIS_URL environment variable. Since this is a demo environment, I wasn’t concerned about configuring separate Redis instances for Action Job or Action Cable. See the hatchbox documentation for setting up Redis and deploying app via them.
Two things I needed configure after setting up Redis were:
enviroments/cable.yml
Make sure it has production setting in cable.yml:
I’m using Hatchbox on a Digital Ocean droplet. When I created the application, Redis was added automatically, which set up the REDIS_URL environment variable. Since this is a demo environment, I wasn’t concerned about configuring separate Redis instances for Action Job or Action Cable. See the hatchbox documentation for setting up Redis and deploying app via them.
Two things I needed configure after setting up Redis were:
enviroments/cable.yml
Make sure it has production setting in cable.yml:
production:
adapter: redis
url: <%= ENV.fetch("REDIS_URL") { "redis://localhost:6379/1" } %>
channel_prefix: wastestart_productionconfig/enviroments/production.rb
Make sure that it has allowed_requests_origin configured. This is for our planex360 domain:
config.action_cable.allowed_request_origins = [/https:\/\/.*\.planex360\.com/]
I could then deploy the app and my turbo streams worked the same as they did in development.