{"action":"created","issue":{"url":"https://api.github.com/repos/rwz/ember-cli-rails/issues/172","labels_url":"https://api.github.com/repos/rwz/ember-cli-rails/issues/172/labels{/name}","comments_url":"https://api.github.com/repos/rwz/ember-cli-rails/issues/172/comments","events_url":"https://api.github.com/repos/rwz/ember-cli-rails/issues/172/events","html_url":"https://github.com/rwz/ember-cli-rails/pull/172","id":87786890,"number":172,"title":"Introduce `ember-cli-deploy` integration","user":{"login":"seanpdoyle","id":2575027,"avatar_url":"https://avatars.githubusercontent.com/u/2575027?v=3","gravatar_id":"","url":"https://api.github.com/users/seanpdoyle","html_url":"https://github.com/seanpdoyle","followers_url":"https://api.github.com/users/seanpdoyle/followers","following_url":"https://api.github.com/users/seanpdoyle/following{/other_user}","gists_url":"https://api.github.com/users/seanpdoyle/gists{/gist_id}","starred_url":"https://api.github.com/users/seanpdoyle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/seanpdoyle/subscriptions","organizations_url":"https://api.github.com/users/seanpdoyle/orgs","repos_url":"https://api.github.com/users/seanpdoyle/repos","events_url":"https://api.github.com/users/seanpdoyle/events{/privacy}","received_events_url":"https://api.github.com/users/seanpdoyle/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-12T16:53:34Z","updated_at":"2015-06-12T16:55:22Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/rwz/ember-cli-rails/pulls/172","html_url":"https://github.com/rwz/ember-cli-rails/pull/172","diff_url":"https://github.com/rwz/ember-cli-rails/pull/172.diff","patch_url":"https://github.com/rwz/ember-cli-rails/pull/172.patch"},"body":"`EmberCLI::Deploy` takes a `namespace` (the name of your app declared in your\ninitializer) and handles all interaction with the Redis instance.\n\nThis is great for `staging` and `production` deploys, but introduces an extra\nstep in the feedback loop during development.\n\nLuckily, `EmberCLI::Deploy` also accepts an `index_html` override, which will\nreplace the call to the Redis instance. This allows integration with the normal\n`ember-cli-rails` workflow:"},"comment":{"url":"https://api.github.com/repos/rwz/ember-cli-rails/issues/comments/111555928","html_url":"https://github.com/rwz/ember-cli-rails/pull/172#issuecomment-111555928","issue_url":"https://api.github.com/repos/rwz/ember-cli-rails/issues/172","id":111555928,"user":{"login":"seanpdoyle","id":2575027,"avatar_url":"https://avatars.githubusercontent.com/u/2575027?v=3","gravatar_id":"","url":"https://api.github.com/users/seanpdoyle","html_url":"https://github.com/seanpdoyle","followers_url":"https://api.github.com/users/seanpdoyle/followers","following_url":"https://api.github.com/users/seanpdoyle/following{/other_user}","gists_url":"https://api.github.com/users/seanpdoyle/gists{/gist_id}","starred_url":"https://api.github.com/users/seanpdoyle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/seanpdoyle/subscriptions","organizations_url":"https://api.github.com/users/seanpdoyle/orgs","repos_url":"https://api.github.com/users/seanpdoyle/repos","events_url":"https://api.github.com/users/seanpdoyle/events{/privacy}","received_events_url":"https://api.github.com/users/seanpdoyle/received_events","type":"User","site_admin":false},"created_at":"2015-06-12T16:55:21Z","updated_at":"2015-06-12T16:55:21Z","body":"We've had some success with this approach on client and internal projects.\r\n\r\nThis approach allows us to not care about Heroku / platform-du-jour installing node / npm / ember and compiling assets, while still enabling us to keep the tight feedback loop provided by `ember-cli-rails` in development.\r\n\r\nI'm not sure about the API, but this is how it has shaken out thusfar.\r\n\r\nWhat do you think?\r\n\r\ncc: @rwz @rondale-sc "}}