Introduce ember-cli-deploy integration
#172
Conversation
|
We've had some success with this approach on client and internal projects. This 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 I'm not sure about the API, but this is how it has shaken out thusfar. What do you think? cc: @rwz @rondale-sc |
`EmberCLI::Deploy` takes a `namespace` (the name of your app declared in your initializer) and handles all interaction with the Redis instance. This is great for `staging` and `production` deploys, but introduces an extra step in the feedback loop during development. Luckily, `EmberCLI::Deploy` also accepts an `index_html` override, which will replace the call to the Redis instance. This allows integration with the normal `ember-cli-rails` workflow:
|
What do you think about this approach @rwz @rondale-sc? Would it be better to start it as an additional gem? |
|
@seanpdoyle This is really cool. Are you thinking about starting an additional gem? I'd be interested in helping. |
|
@aaronrenner that sounds great, I'd love to have some help. Would you like to review my port of this implementation? seanpdoyle/ember-cli-rails-deploy-redis#1 The same invite goes out to @rwz and @rondale-sc I'll close this PR once I get integration working |
Extracted from a PR against [ember-cli-rails]. `EmberCLI::Deploy` takes a `namespace` (the name of your app declared in your initializer) and handles all interaction with the Redis instance. This is great for `staging` and `production` deploys, but introduces an extra step in the feedback loop during development. Luckily, `EmberCLI::Deploy` also accepts an `index_html` override, which will replace the call to the Redis instance. This allows integration with the normal `ember-cli-rails` workflow: [ember-cli-rails]: tricknotes/ember-cli-rails#172
|
Closing in favor of https://github.com/seanpdoyle/ember-cli-rails-deploy-redis/releases/tag/v0.0.1 @rwz @rondale-sc should we mention that Gem in the Readme? |
EmberCLI::Deploytakes anamespace(the name of your app declared in yourinitializer) and handles all interaction with the Redis instance.
This is great for
stagingandproductiondeploys, but introduces an extrastep in the feedback loop during development.
Luckily,
EmberCLI::Deployalso accepts anindex_htmloverride, which willreplace the call to the Redis instance. This allows integration with the normal
ember-cli-railsworkflow: