Merge branch 'stage'

Author: aklkv

.gitignore

@@ -15,3 +15,4 @@
 /libpeerconnection.log
 npm-debug.log
 testem.log
+.DS_Store

.travis.yml

@@ -23,3 +23,11 @@ script:
   - if [ "$TRAVIS_BRANCH" == "dev" ]; then ember deploy development --verbose; elif
     [ "$TRAVIS_BRANCH" == "stage" ]; then ember deploy staging --verbose; elif [ "$TRAVIS_BRANCH"
     == "master" ]; then ember deploy production --verbose; fi
+
+# notifications:
+#   slack:
+#     rooms:
+#       secure: HRNtdw5i2RaK6dD6wp0Y76U2Mc+SMoK9LnIHXoKnnDpkNnHyNpcKyFUq9neVx1lR5QwonjH1Icg2MGU8v/lmhIdwa7d62tVWQBhV7C6Cg+KcnMRTMQesT549EH+Lmk0Gjv9aAG6mcQFubuWbDRrOb1oDMviGlB0dGSK0ryn4hYp8XBeyG+RG8ruI6t94sdKTVePbfmhOPoiUWLXqEcqgBlWP/Gq3WbVxTlGiXdDGtcoDGklGMD7o4Dx3BwQR7r+18Km3bFncX3jmaqmycqbY4vcdpe+wNggHWwIUyV84isR00oGemLluN/BdswP17KiucVCg1VLt+saoyY1AGV39TEQww1XOjy7ThjHWJbee1vSMMODGcG/7eD87g+CJovYHXbSlIe7FCqJgD+tXI8OAvP36rcvEv6Ao5RhpR+/OahiJoLrl/fz/gQxsQSVVRoZKoit7fcpGjOQrG17p2pEPzeVbIP/PtC9HHx5OCSiKWMpfA9+GoEDt4TB5h8JQDoNecTx671RL2SOb5RSVjjS0gg6zyRmXuYBPdVw7e2L8LJWW9FlfAENRmCNp8g9CKqOVLoivvZzL6H74u0L5Ej3xbuoaBTczzhNsA/hA+d8WIrut1Ug0yfbGKAF01nioBRU/TlirUSGY121LjWOxSicGaPFzkmkXGefdHu8xmbK0X3A=
+# addons:
+#   code_climate:
+#     repo_token: a03140c91dbbbf084ff05caefb45c0a520f595dd417ec46934aa45e43f06585c

slides/img/profile.jpg

@@ -16,7 +16,7 @@ autoscale: true
 Alexey (*Alex*) Kulakov
 
 
-- SemiosBIO
+- Semios
 - @akulakov
 - aklkv.com
 
@@ -33,223 +33,55 @@ Alexey (*Alex*) Kulakov
 
 ![right 80%](./img/ember-cli-deploy.png)
 
-- Pipeline Hooks
-- Configuration
-- Usage & Deployment Strategies
-- Plugins and plugin packs
-
-^
-Ember CLI Deploy is an addon that provides a single interface for deploying Ember applications.
-Just as any Ember app is served with ember serve and built with ember build, any app using Ember CLI Deploy is deployed with the same command: ember deploy.
-To achieve this, Ember CLI Deploy structures your app’s deployment using a deploy pipeline, which consists of several pipeline hooks. These standard hooks are the foundation for a rich ecosystem of plugins which you can compose to create a deployment process suitable for your application.
-Whether you need to compress or encode assets, upload your files to a private server or to AWS, or notify a Slack channel after a successful deploy, Ember CLI Deploy is up to the task. Keep reading to learn more.
-
-
----
-### Pipeline Hooks
-
-`ember deploy`
-
-- configure
-- setup
-- willDeploy
-- willBuild, build, didBuild,
-- willPrepare, prepare, didPrepare,
-- fetchInitialRevisions,
-- willUpload, upload, didUpload,
-- willActivate, activate, fetchRevisions, didActivate
-- fetchRevisions
-- teardown
-
----
-
-`ember deploy:activate`
-
-- configure
-- setup
-- fetchInitialRevisions
-- willActivate
-- activate
-- fetchRevisions
-- didActivate
-- teardown
-
----
-
-`ember deploy:list`
-
-- configure
-- setup
-- fetchRevisions
-- displayRevisions
-- teardown
-
-`didFail`
-
----
-### Context Example
-
-![100%](./img/context-example.gif)
-
----
-
-### Configuration
-
-```javascript
-  // deploy.js (sync)
-  module.exports = function(environment){
-    var ENV = {
-    };
-
-    if (environment === 'production') {
-      ENV.redis = {
-        url: process.env.REDIS_URL
-      }
-    };
-    return ENV;
-  };
-```
+- [Introduction to ember-cli-deploy by Mattia Gheda](https://vimeo.com/158447249)
+- [EmberCamp London 2015: Ember CLI Deploy by Aaron Chambers and Luke Melia](https://www.youtube.com/watch?v=fcSL5poJ1gQ)
 
 ---
 
-### Additional Environments
-
-```javascript
-  // config/environment.js
-  module.exports = function(environment){
-  var ENV = {
-  };
-
-  if (environment === 'qa') {
-    ENV.build.environment = 'development';
-  };
-  if (environment === 'staging') {
-    ENV.build.environment = 'production';
-  };
-  return ENV;
-  };
-```
-
-^
-If you need to have the original environment that was passed into the ember build command, this can be obtained under the environment variable of `DEPLOY_TARGET` and referenced in any node.js context with `process.env.DEPLOY_TARGET`.
+#### Ember-cli + AWS S3 (CloudFront) via travis-ci
+![inline](./img/diagram.png)
 
 ---
 
-### dotEnv Support
+### Ember-cli-deploy AWS pack
 
-^
-It is often common to store sensitive data in environment variables and access them via `process.env` in the likes of `config/deploy.js`.
+- [ember-cli-deploy-aws-pack](https://github.com/kpfefferle/ember-cli-deploy-aws-pack)
+- [Deploying Ember to AWS CloudFront](http://blog.testdouble.com/posts/2015-11-03-deploying-ember-to-aws-cloudfront-using-ember-cli-deploy.html)
 
 ```bash
-  # /.env
-
-  AWS_KEY=123456
-  AWS_SECRET=abcdef
-```
-
----
-
-```javascript
-  // config/deploy.js
-  module.exports = function(deployTarget) {
-  var ENV = {
-    s3: {
-      accessKeyId: process.env.AWS_KEY,
-      secretAccessKey: process.env.AWS_SECRET
-    }
-  };
-
-  return ENV;
-  };
-```
-
----
-
-###Deploy-Target Specific Variables
-
-`ember deploy staging`
-
-``` bash
-  # /.env.deploy.staging
-
-  AWS_KEY=78910
-  AWS_SECRET=ghijkl
-```
-
----
-
-```javascript
-
-  // config/deploy.js
-  module.exports = function(deployTarget) {
-    var ENV = { };
-
-    if (deployTarget === 'staging') {
-      ENV.s3 = {
-        accessKeyId: process.env.AWS_KEY,
-        secretAccessKey: process.env.AWS_SECRET
-      };
-    }
-
-    return ENV;
-  };
+ember install ember-cli-deploy
+ember install ember-cli-deploy-aws-pack
 ```
-^
-.gitignore
-Remember to add all `.env` and `.env.deploy.<deploy-target>` files to your `.gitignore` file so you don’t accidentally expose sensitive information.
-
-
----
-
-### Usage & Deployment Strategies
-
-- `ember deploy`
-
-^
-runs main pipeline
-
-- `ember deploy production`
 
 ^
-production pipeline
-
-- `ember deploy:activate production --revision=43cc587`
-
-^
-`--revision` key is mandatory
-
-- `ember deploy:list`
-- `ember deploy:list production`
+- deploy.js
+- environment.js
+- templates/application.js
+- controllers/application.js
 
 ---
 
-### Example time
+![inline 90%](./img/travis-ci.png)
 
-![inline](https://m.popkey.co/3bcbd8/AoYjv.gif)
+- travis-ci.com
+  - private
+- travis-ci.org
+  - public
+  - free
 
 ^
-- `ember new <app-name>`
-- `ember install ember-cli-deploy`
-- `ember install ember-cli-deploy-aws-pack`
+- travis.yml
 
 ---
 
-### Let's make it even more awesome
-
-#### Ember-cli + AWS S3 (CloudFront) via travis-ci
-![inline](./img/diagram.png)
+##
 
----
+```bash
+  ember deploy <development target>
+```
 
-![inline 90%](./img/travis-ci.png)
 
-- travis-ci.com
-  - private
-- travis-ci.org
-  - public
-  - free
 
----
 
 ```bash
     # .travis.yml
@@ -259,6 +91,11 @@ production pipeline
       == "master" ]; then ember deploy production --verbose; fi
 ```
 
+---
+
+![inline](https://m.popkey.co/3bcbd8/AoYjv.gif)
+
+
 ---
 
 ![left 90%](./img/semios.png)
@@ -267,3 +104,11 @@ production pipeline
 
 - [email protected]
 - semios.com
+
+---
+
+### Thank you
+
+- [source code and slides](https://github.com/aklkv/emberjs-talk-example)
+
+---