update docs

Author: gentele

docs/docs/cli/add.md

@@ -0,0 +1,17 @@
+---
+title: devspace add
+---
+
+With `devspace add`, you can add ports for portForwarding and paths to the sync configuration.
+
+```bash
+Usage:
+  devspace add [command]
+
+Available Commands:
+  port        Lists port forwarding configuration
+  sync        Add a sync path to the devspace
+
+Flags:
+  -h, --help   help for add
+```

docs/docs/cli/init.md

@@ -13,8 +13,8 @@ Flags:
   -l, --language string           Programming language of your project
   -o, --overwrite                 Overwrite existing chart files and Dockerfile
   -r, --reconfigure               Change existing configuration
-      --templateRepoPath string   Local path for cloning chart template repository (uses temp
-folder if not specified)
+      --templateRepoPath string   Local path for cloning chart template repository (uses temp folder
+if not specified)
       --templateRepoUrl string    Git repository for chart templates (default "https://github.com/covexo/devspace-templates.git")
 ```
 

docs/docs/cli/remove.md

@@ -0,0 +1,17 @@
+---
+title: devspace remove
+---
+
+With `devspace remove`, you can remove ports from the portForwarding and paths from the sync configuration.
+
+```bash
+Usage:
+  devspace remove [command]
+
+Available Commands:
+  port        Removes forwarded ports from a devspace
+  sync        Remove sync paths from the devspace
+
+Flags:
+  -h, --help   help for remove
+```

docs/docs/cli/up.md

@@ -9,15 +9,15 @@ Usage:
   devspace up [flags]
 
 Flags:
-  -b, --build            Build image if Dockerfile has been modified (default true)
-  -h, --help             help for up
-      --init-registry    Install or upgrade Docker registry (default true)
-      --no-sleep         Enable no-sleep
-  -o, --open string      Install/upgrade tiller (default "cmd")
-      --portforwarding   Enable port forwarding (default true)
-  -s, --shell string     Shell command (default: bash, fallback: sh)
-      --sync             Enable code synchronization (default true)
-      --tiller           Install/upgrade tiller (default true)
+  -b, --build             Build image if Dockerfile has been modified (default true)
+  -d, --deploy            Deploy chart
+  -h, --help              help for up
+      --init-registries   Initialize registries (and install internal one) (default true)
+      --no-sleep          Enable no-sleep
+      --portforwarding    Enable port forwarding (default true)
+  -s, --shell string      Shell command (default: bash, fallback: sh)
+      --sync              Enable code synchronization (default true)
+      --tiller            Install/upgrade tiller (default true)
 ```
 
 **Note**: Every time you run `devspace up`, your containers will be re-deployed. This way, you will always start with a clean state.

docs/docs/configuration/config.yaml.md

@@ -7,8 +7,8 @@ This is an example of a [.devspace/config.yaml](#)
 version: v1
 devSpace:
   release:
-    name: devspace-cloud-com
-    namespace: dev-gentele
+    name: my-project
+    namespace: my-namespace
   portForwarding:
   - resourceType: pod
     labelSelector:
@@ -24,23 +24,43 @@ devSpace:
       release: my-app
     localSubPath: ./
     containerPath: /app
-image:
-  name: devspace
-services:
-  registry:
-    internal:
-      release:
-        name: devspace-registry
-        namespace: dev-gentele
+images:
+  default:
+    name: devspace-user/devspace
+    tag: 9u5ye0G
+    registry: default
+    build:
+      engine:
+        docker:
+          enabled: true
+          preferMinikube: true
+  database:
+    name: devspace-user/devspace
+    tag: 62i5e2p
+    registry: internal
+    build:
+      engine:
+        kaniko:
+          enabled: true
+registries:
+  default:
+    url: hub.docker.com
+  internal:
     user:
       username: user-XXXXX
       password: XXXXXXXXXX
+services:
+  internalRegistry:
+    release:
+      name: devspace-registry
+      namespace: my-namespace
   tiller:
+    appNamespaces:
+    - my-namespace
     release:
-      namespace: dev-gentele
+      namespace: my-namespace
 cluster:
   useKubeConfig: true
-
 ```
 A [.devspace/config.yaml](#) contains any public/shared configuration for running a DevSpace for the respective project. It is highly recommended to put this file under version control (e.g. git add).
 
@@ -72,22 +92,31 @@ To comfortably sync code to a DevSpace, the DevSpace CLI allows to configure rea
 
 In the example above, the entire code within the project would be synchronized with the folder `/app` inside the DevSpace.
 
-## image
-An image is defined by:
+## images
+This section of the config defines a map of images that can be used in the helm chart that is deployed during `devspace up`. An image is defined by:
 - `name` of the image that is being pushed to the registry
 - `tag` stating the latest tag pushed to the registry
-- `buildTime` (time of the latest image build process, i.e. docker build)
+- `registry` referencing one of the keys defined in the `registries` map
+- `build` defining the build procedure for this image
 
-## services
-Defines additional services for your DevSpace.
+## images[*].build
+An image build is mainly defined by the build engine. There are 2 build engines currently supported:
+- `docker` uses the local Docker daemon or a Docker daemon running inside a Minikube cluster (if `preferMinikube` == true)
+- `kaniko` builds images in userspace within a build pod running inside the Kubernetes cluster
 
-### services.registry
-The `registry` field specifies:
-- `external` tells the DevSpace CLI to push to an external registry (format: myregistry.com:port)
-- `internal` defines a private cluster-internal registry by defining a `release` for it
+## registries
+This section of the config defines a map of image registries. You can use any external registry or link to the [services.internalRegistry](#services-internal-registry)
+- `url` of the registry (format: myregistry.com:port)
 - `user` credentials (`username`, `password`) for pushing to / pulling from the registry
 - `insecure` flag to allow pushing to registries without HTTPS
 
+## services
+Defines additional services for your DevSpace.
+
+### services.internalRegistry
+The `internalRegistry` is used to tell the DevSpace CLI to deploy a private registry inside the Kubernetes cluster:
+- `release` for deploying the registry (see [Type: Release](#type-release))
+
 ### services.tiller
 The `tiller` service is defined by:
 - `release` definition for tiller (see [Type: Release](#type-release))

docs/docs/configuration/dockerfile.md

@@ -2,9 +2,9 @@
 title: /Dockerfile
 ---
 
-The Dockerfile specifies how your main development image has to be built. You can add files, install dependencies, set environment variables and run any other command. 
+A Dockerfile specifies how a build engine (e.g. Docker or kaniko) will assemble a Docker image. You can add files, install dependencies, set environment variables and run any other command. 
 
-When you run `devspace init` or `devspace up`, the DevSpace CLI will add an exemplary Dockerfile for your project. You can modify the Dockerfile according to your needs.
+When you run `devspace init` or `devspace up`, the DevSpace CLI will add an exemplary Dockerfile for your project if you do not already have one, yet. You can modify the Dockerfile according to your needs. You can also have multiple Dockerfiles within your project and let the DevSpace CLI build and push them accordingly (see [config.yaml](config.ymal.html)).
 
 See the official Docker documentation for **"[Best practices for writing Dockerfiles](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/)"**
 

docs/website/sidebars.json

@@ -13,6 +13,8 @@
       "cli/up",
       "cli/down",
       "cli/reset",
+      "cli/add",
+      "cli/remove",
       "cli/install",
       "cli/upgrade"
     ],