eileencodes 19e7f65dd1 Don't log Action Cable to STDOUT in development ... Logging Action Cable to STDOUT caused the development log to see double messages like this: ``` Started GET "/" for ::1 at 2015-12-17 15:21:34 -0500 Started GET "/" for ::1 at 2015-12-17 15:21:34 -0500 Processing by Rails::WelcomeController#index as HTML Processing by Rails::WelcomeController#index as HTML Rendered /welcome/index.html.erb (0.0ms) Rendered /welcome/index.html.erb (0.0ms) Completed 200 OK in 3ms (Views: 1.3ms | ActiveRecord: 0.0ms) Completed 200 OK in 3ms (Views: 1.3ms | ActiveRecord: 0.0ms) ``` Now that Action Cable is part of Rails it doesn't need it's own logger and will log to STDOUT via the local dev server here: https://github.com/rails/rails/blob/master/railties/lib/rails/commands/server.rb		2015-12-17 15:30:40 -05:00
..
action_cable	Don't log Action Cable to STDOUT in development	2015-12-17 15:30:40 -05:00
assets/javascripts	Move Cable to ActionCable for client-side constant to avoid conflicts	2015-12-16 15:29:21 +01:00
rails/generators/channel	Update USAGE	2015-12-17 10:17:52 -05:00
action_cable.rb	Initial stab at adding Action Cable to rails/master	2015-12-14 16:38:37 +01:00