Setup deploy pipeline for development and production

Author: erikap

config/deploy.js

@@ -0,0 +1,43 @@
+/* eslint-env node */
+'use strict';
+
+module.exports = function(deployTarget) {
+  //see https://github.com/ember-cli-deploy/ember-cli-deploy-revision-data/issues/52
+  process.env.GIT_DISCOVERY_ACROSS_FILESYSTEM=1;
+  let ENV = {
+    build: {
+      environment: 'development'
+    },
+    'ssh-index': { // copy and deploy index.html
+      username: 'root',
+      host: 'semantic.works',
+      port: 22,
+      // remoteDir:
+      allowOverwrite: true,
+      agent: process.env.SSH_AUTH_SOCK
+    },
+    'rsync': { // copy assets
+      host: '[email protected]',
+      port: 22,
+      // dest: '/data/app-semantic-works/frontend-semantic-works',
+      delete: false,
+      arg:['--verbose']
+    }
+  };
+
+  if (deployTarget === 'development' || deployTarget === 'dev') {
+    ENV['ssh-index']["remoteDir"] = "/data/app-semantic-works-dev/frontend-semantic-works",
+    ENV['rsync']['dest'] = ENV['ssh-index']['remoteDir'];
+  }
+
+  if (deployTarget === 'production') {
+    ENV.build.environment = "production";
+    ENV['ssh-index']["remoteDir"] = "/data/app-semantic-works/frontend-semantic-works",
+    ENV['rsync']['dest'] = ENV['ssh-index']['remoteDir'];
+  }
+
+  // Note: if you need to build some configuration asynchronously, you can return
+  // a promise that resolves with the ENV object instead of returning the
+  // ENV object synchronously.
+  return ENV;
+};

package.json

@@ -27,6 +27,12 @@
     "ember-cli-app-version": "^3.2.0",
     "ember-cli-babel": "^7.13.0",
     "ember-cli-dependency-checker": "^3.2.0",
+    "ember-cli-deploy": "^1.0.2",
+    "ember-cli-deploy-build": "^2.0.0",
+    "ember-cli-deploy-display-revisions": "^2.0.0",
+    "ember-cli-deploy-revision-data": "^1.0.0",
+    "ember-cli-deploy-rsync": "0.0.5",
+    "ember-cli-deploy-ssh-index": "^1.0.0",
     "ember-cli-eslint": "^5.1.0",
     "ember-cli-htmlbars": "^4.2.0",
     "ember-cli-inject-live-reload": "^2.0.1",