I am working on an Ember-Rails application. I previously used Yeoman to create applications without ember-rails and js plugins, and I would love to be able to realize the benefits of Yeoman (especially Grunt livereload) when working on my Ember-Rails projects. However, I am not sure if Ember, Rails and Yeoman are compatible and whether they coincide with their roles and responsibilities. For example:
Dependency Management
- I understand that Bower is used to manage dependencies. Does Bauer affect how assets are loaded through the rail resource pipeline? What are the advantages / disadvantages of loading dependencies using Bower instead of using Rails stones?
LiveReload
- Does the pusheload function work with a single-page application (for example, an embedded Ember) in the same way as with a multi-page application (for example, on an html site that does not use a js framework)? Are individual models / views / controllers updated or reloading and / or recompiling the entire application through the Rails pipeline?
Existing project
- Are there any problems integrating Yeoman into an existing Ember-Rails application? We use Ember 1.3.0-beta and Ember Data 1.0.0-beta in our production. If you have experience with modern Ember builds, are Ember-auth and Ember data compatible with Yeoman?
If someone has experience combining Ember, Rails and Yeoman, or if you understand how the interface and backend will compare with such a stack, share your thoughts! Would you recommend just integrating part of the Yeoman configuration (e.g. Grunt) with the Ember-Rails app instead of all Yeoman?
Thanks.
source
share