Bring Sanity to Frontend Infrastructure with Ember
summary
Ember and ember-cli give concrete answers: use ember build creates a dist as the deploy unit, automate with an ember-deploy add-on so CI just runs a command, and replace repeated test wiring with an XHR interceptor / backend-in-the-browser add-on that provides fixtures and factories for end-to-end tests. Semantic versioning plus ember-data and the CLI upgrade flow let many independent frontends stay consistent, upgradeable, and easy for any developer to pick up and maintain.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:22Acme's Infrastructure
- 3:31Front End Infrastructure
- 10:04Authentication
- 11:57Testing
- 19:04Closing Thoughts
- 20:14Ember Is Not Just a Framework
- 21:44Let Them Innovate
related talks
34mSoftware Productivity and Ember: Ember CLI
26mModern Javascript Frameworks - Introduction to Ember.JS and Ember-CLI
28mEmber CLI, The Next Generation
25mThe Great Migration, Redesigning and Rewriting our App in Ember.js
35mPanel: Ember – Why and Where?
39mRails and EmberCLI: an integration love story
22mUsing Ember to Make the Seemingly Impossible Easy
40mSurprise Talk