From 4213825a9ac5111660a7818fff283b9ad659f044 Mon Sep 17 00:00:00 2001 From: Prathamesh Sonpatki Date: Sun, 28 Feb 2016 20:16:56 +0530 Subject: Fix merge conflict in Action Cable guide [ci skip] --- guides/source/action_cable_overview.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'guides') diff --git a/guides/source/action_cable_overview.md b/guides/source/action_cable_overview.md index 047c163ee2..964cb882c5 100644 --- a/guides/source/action_cable_overview.md +++ b/guides/source/action_cable_overview.md @@ -546,7 +546,6 @@ You can change that in `config/database.yml` through the `pool` attribute. ## Running standalone cable servers -<<<<<<< HEAD ### In App Action Cable can run alongside your Rails application. For example, to @@ -569,10 +568,8 @@ your server spawns, you will also have a new instance of ActionCable, but the use of Redis keeps messages synced across connections. ### Standalone -The cable server(s) can be separated from your normal application server. -======= -The cable servers can be separated from your normal application server. ->>>>>>> Further cleanup of the cable guide + +The cable servers can be separated from your normal application server. It's still a Rack application, but it is its own Rack application. The recommended basic setup is as follows: -- cgit v1.2.3