README.md in open-dock-0.1.1 vs README.md in open-dock-0.1.2

@@ -136,33 +136,35 @@
 #  interactive: true
 #  memory: 8g
 #  cpuset: 0-7
 
 # POST-CONDITIONS: execute after build the container:
-  post-conditions:
-    - sshpass -p 'J3mw?$_6' ssh-copy-id -o 'StrictHostKeyChecking no' -i ~/.ssh/id_rsa.pub [e-mail] -p 2222
-    - ssh [e-mail] -p 2222 "echo 'root:Kxxxxx1' | chpasswd"
+#  post-conditions:
+#    - sshpass -p 'J3mw?$_6' ssh-copy-id -o 'StrictHostKeyChecking no' -i ~/.ssh/id_rsa.pub [e-mail] -p 2222
+#    - ssh [e-mail] -p 2222 "echo 'root:Kxxxxx1' | chpasswd"
 
 # here you can create other containers
 # db:
 #   hostname: db.lebrijo.com
 #   image: ubuntu/postgresql
 ```
 
 `ops ship example.com` will create all containers configured on 'containers/example.com.yml' file
 
+Note: host SSH credentials (id_rsa.pub and authorized_keys) are copied by default to container, in order to have the same access to conainer.
+
 ### Shipping your local Docker
 
 You can create a file `containers/localhost.example.com.yml` where you can define containers. And launch them on your workstation:
 
 ```
 ops ship localhost.example.com
 ```
 
 By convention:
 
-* If [host_name] include "localhost" string, it is assumed that containers are shipped on local workstation
+* If [host_name] includes "localhost" string, it is assumed that containers are shipped as docker containers in local workstation
 
 ## Configure Containers (are nodes for Chef)
 
 Configuration with chef commands
 
@@ -187,10 +189,11 @@
 * `ops exec HOST_NAME "COMMAND"` execute any command on a host remotely (i.e. ops exec example.com 'docker ps -a')
 * `ops ship HOST_NAME` run the containers in the host.
 * `ops unship HOST_NAME`
 * TODO: `ops reship HOST_NAME` unship/ship all containers from host.
 * `ops configure HOST_NAME` configure all containers with chef.
+* TODO: `ops ssh [CONTAINER_NAME] HOST_NAME` ssh connection to host or container
 
 ## Create your infrastructure project (/ops)
 
 OPS command is focused to cover first Provision configurations for a the Operations of your infrastructure.
 
@@ -260,6 +263,10 @@
 Create command `ops configure [host_name]` this will cook all containers. By convention:
 
 * "root" is the user in all containers
 * Each container configuration is defined in a Chef node: `nodes/[container_name].[host_name].json`
 * Then you have to create all container name records in your DNS provider: `[container_name].[host_name]   CNAME   [host_name].`
-* If [host_name] include "localhost" string, it is assumed that containers are shipped on local workstation
+* If [host_name] include "localhost" string, it is assumed that containers are shipped on local workstation
+
+### v0.1.2
+
+* Delete post-conditions from containers files. By default host credentials are passed to conainers.
\ No newline at end of file