Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Allow actioncable connections from any port in development | Michael Dever | 2016-06-16 | 1 | -1/+1 |
| | |||||
* | Properly support reloading for Action Cable channels | Matthew Draper | 2016-06-02 | 1 | -5/+2 |
| | |||||
* | renames ActionCable::Railtie to ActionCable::Engine | Xavier Noria | 2016-05-04 | 1 | -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 .js | Javan Makhmali | 2016-03-03 | 1 | -1/+1 |
| | |||||
* | Use AS::Executor / AS::Reloader to support reloading in ActionCable | Matthew Draper | 2016-03-02 | 1 | -0/+25 |
| | |||||
* | Enable Action Cable routes by default | Jon Moss | 2016-02-24 | 1 | -1/+12 |
| | | | | This also marks Action Cable routes as internal to Rails. | ||||
* | Default connection class to ActionCable::Connection::Base. | Kasper Timm Hansen | 2016-02-14 | 1 | -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 Hansen | 2016-02-14 | 1 | -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 @kaspth | Jon Moss | 2016-01-18 | 1 | -1/+1 |
| | |||||
* | Adapterize ActionCable storage and extract behavior | Jon Moss | 2016-01-18 | 1 | -3/+3 |
| | |||||
* | Another stab at only mounting redis if the config is there | David Heinemeier Hansson | 2015-12-16 | 1 | -2/+2 |
| | |||||
* | Assume that the cable server is running in-process by default, offer option ↵ | David Heinemeier Hansson | 2015-12-16 | 1 | -0/+2 |
| | | | | to change that in config/environments/production.rb | ||||
* | Doh, should have read ff370ee61754b00f864f3ddd0af62be4dfa0de67 | David Heinemeier Hansson | 2015-12-16 | 1 | -0/+36 |
| | | | | Indeed we need this to be an engine for the internal assets to work | ||||
* | We are using railtie, not engine | David Heinemeier Hansson | 2015-12-16 | 1 | -36/+0 |
| | |||||
* | Move the require to the right place | Rafael Mendonça França | 2015-12-15 | 1 | -0/+1 |
| | |||||
* | Configure the Action Cable's redis in the engine | Rafael Mendonça França | 2015-12-15 | 1 | -0/+5 |
| | | | | This will decouple Action Cable from Rails. | ||||
* | Action Cable need to be a engine | Rafael Mendonça França | 2015-12-15 | 1 | -0/+30 |
| | | | | Otherwise assets will not work | ||||
* | Switch from engine to railtie | David Heinemeier Hansson | 2015-12-15 | 1 | -30/+0 |
| | |||||
* | Hook in ActionView::Base, not in ApplicationController | Rafael Mendonça França | 2015-12-14 | 1 | -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 engine | Rafael Mendonça França | 2015-12-14 | 1 | -0/+1 |
| | |||||
* | Get ready to merge into Rails | David Heinemeier Hansson | 2015-12-14 | 1 | -0/+27 |