documentation extended; deploment.config cleaned

Author: Robin Buschmann

.ebextensions/deployment.config

@@ -20,11 +20,6 @@
       "option_name": "ELBSubnets",
       "value": "subnet-09f63d61"
     },
-    {
-      "namespace": "aws:autoscaling:launchconfiguration",
-      "option_name": "InstanceType",
-      "value": "t2.nano"
-    },
     {
       "namespace": "aws:autoscaling:launchconfiguration",
       "option_name": "SecurityGroups",

README.md

@@ -49,6 +49,12 @@ The policy should look like this:
 }
 ````
 
+#### Saved configurations (aws)
+
+There are currently 2 saved configurations for the intercharge application:
+ - `intercharge-dev`
+ - `intercharge-prod`
+
 ### Environment variables
 
 The application needs some environment variables for configuration.
@@ -106,6 +112,16 @@ MYSQL/Aurora | TCP      | 3306       | sg-?????
 
 ````
 
+### Deployment via eb-cli
+
+#### Creating new environment in elasticbeanstalk via eb-cli
+
+From the repo directory call `eb create <ENVIRONMENT_NAME> --cfg <SAVED_CONFIG_NAME>` to create a new environment. Pass one of the available configurations to create either a production or a development/qa instance.
+
+#### Deploy new versions
+
+From the repo directory select the environment, which should be updated (`eb use <ENVIRONMENT_NAME>`) and call `eb deploy`. Therefore the last changes have to be pushed to the remote repo.
+
 ## Running node.js server
 
 To start the server use `ENVIRONMENT={development|production} ... DB_HOST={string} npm start` in command line.