The second option is to pass the server url through the `action_cable_meta_tag` in your layout.
This uses a url or path typically set via `config.action_cable.url` in the environment configuration files, or defaults to "/cable".
The second option is to pass the server URL through the `action_cable_meta_tag` in your layout.
This uses a URL or path typically set via `config.action_cable.url` in the environment configuration files, or defaults to "/cable".
This method is especially useful if your WebSocket url might change between environments. If you host your production server via https, you will need to use the wss scheme
This method is especially useful if your WebSocket URL might change between environments. If you host your production server via https, you will need to use the wss scheme
for your Action Cable server, but development might remain http and use the ws scheme. You might use localhost in development and your
domain in production.
In any case, to vary the WebSocket url between environments, add the following configuration to each environment:
In any case, to vary the WebSocket URL between environments, add the following configuration to each environment: