aboutsummaryrefslogtreecommitdiffstats
path: root/actioncable/lib/action_cable/engine.rb
Commit message (Collapse)AuthorAgeFilesLines
* renames ActionCable::Railtie to ActionCable::EngineXavier Noria2016-05-041-1/+1
| | | | | | | | This is an engine living in action_cable/engine.rb, convention is to call these things *::Engine. Looking at thi git history looks like the current *::Railtie was just an accident.
* Share default mount path with client side .jsJavan Makhmali2016-03-031-1/+1
|
* Use AS::Executor / AS::Reloader to support reloading in ActionCableMatthew Draper2016-03-021-0/+25
|
* Enable Action Cable routes by defaultJon Moss2016-02-241-1/+12
| | | | This also marks Action Cable routes as internal to Rails.
* Default connection class to ActionCable::Connection::Base.Kasper Timm Hansen2016-02-141-0/+4
| | | | | | | Instead of depending on ApplicationCable::Connection being defined at initialize we should inject it in the Railtie. Thus we can kill more setup in the tests too.
* Inject Rails' channel paths in engine.Kasper Timm Hansen2016-02-141-0/+2
| | | | | | | | | | | | | We were explicitly referencing Rails.root in ActionCable::Server::Configuration.initialize, thereby coupling ourselves to Rails. Instead add `app/channels` to Rails' app paths and assign the existent files to `channel_paths`. Users can still append to those load paths with `<<` and `push` in `config/application.rb`. This means we can remove the custom `Dir` lookup in `channel_paths` and the Rails and root definitions in the tests.
* config_opts => cable, per @kaspthJon Moss2016-01-181-1/+1
|
* Adapterize ActionCable storage and extract behaviorJon Moss2016-01-181-3/+3
|
* Another stab at only mounting redis if the config is thereDavid Heinemeier Hansson2015-12-161-2/+2
|
* Assume that the cable server is running in-process by default, offer option ↵David Heinemeier Hansson2015-12-161-0/+2
| | | | to change that in config/environments/production.rb
* Doh, should have read ff370ee61754b00f864f3ddd0af62be4dfa0de67David Heinemeier Hansson2015-12-161-0/+36
| | | | Indeed we need this to be an engine for the internal assets to work
* We are using railtie, not engineDavid Heinemeier Hansson2015-12-161-36/+0
|
* Move the require to the right placeRafael Mendonça França2015-12-151-0/+1
|
* Configure the Action Cable's redis in the engineRafael Mendonça França2015-12-151-0/+5
| | | | This will decouple Action Cable from Rails.
* Action Cable need to be a engineRafael Mendonça França2015-12-151-0/+30
| | | | Otherwise assets will not work
* Switch from engine to railtieDavid Heinemeier Hansson2015-12-151-30/+0
|
* Hook in ActionView::Base, not in ApplicationControllerRafael Mendonça França2015-12-141-2/+4
| | | | | | The application can have more than one ApplicationController and we want Action Cable helpers in all controllers and their views so we should hook in the same place that others helpers.
* Require the top level file in the engineRafael Mendonça França2015-12-141-0/+1
|
* Get ready to merge into RailsDavid Heinemeier Hansson2015-12-141-0/+27