docs: add v6 structure and content

Author: LukasGentele

cmd/init.go

@@ -443,15 +443,14 @@ echo 'Anyone using this project can invoke it via "devspace run migrate-db"'`,
 
 	// Add pipeline: dev
 	config.Pipelines["dev"] = &latest.Pipeline{
-		Run: `
-run_dependencies --all     # 1. Deploy any projects this project needs (see "dependencies")
-create_deployments --all   # 2. Deploy Helm charts and manifests specfied as "deployments"
-start_dev ` + imageName + `                     # 3. Start dev mode "` + imageName + `" (see "dev" section)`,
+		Run: `run_dependencies --all       # 1. Deploy any projects this project needs (see "dependencies")
+create_deployments --all     # 2. Deploy Helm charts and manifests specfied as "deployments"
+start_dev ` + imageName + `                # 3. Start dev mode "` + imageName + `" (see "dev" section)`,
 	}
 
 	// Add pipeline: dev
 	config.Pipelines["deploy"] = &latest.Pipeline{
-		Run: `run_dependencies --all                    # 1. Deploy any projects this project needs (see "dependencies")
+		Run: `run_dependencies --all                            # 1. Deploy any projects this project needs (see "dependencies")
 build_images --all -t $(git describe --always)    # 2. Build, tag (git commit hash) and push all images (see "images")
 create_deployments --all                          # 3. Deploy Helm charts and manifests specfied as "deployments"`,
 	}

docs/pages/_partials/info-component-chart.mdx

@@ -1,3 +1,3 @@
 :::info Component Chart Docs
-The component chart is a flexible Helm chart for deploying custom applications in a standardized manner. Learn more in the **[Component Chart Documentation](https://devspace.sh/component-chart/docs/introduction)**.
+The component chart is a flexible Helm chart for deploying custom applications in a standardized manner. Learn more about **[configuring component-chart deployments](../configuration/deployments/helm/chart/component-chart.mdx)**.
 :::

docs/pages/_partials/kubectl-options-applyArgs.mdx

@@ -4,11 +4,6 @@ The `applyArgs` option expects an array of strings stating additional arguments
 Even if you set `kustomize: true`, DevSpace only renders the manifest templates using kustomize but the actual deployment will be executed using `kubectl apply`.
 :::
 
-#### Default Value for `applyArgs`
-```yaml
-applyArgs: []
-```
-
 #### Example: Custom Kubectl Args & Flags
 ```yaml
 deployments:
@@ -22,7 +17,6 @@ deployments:
       - "--grace-period"
       - "30"
 ```
-**Explanation:**  
 Deploying the above example would roughly be equivalent to this command:
 ```bash
 kubectl apply --timeout=10s --grace-period=30 -f backend/

docs/pages/_partials/kubectl-updateImageTags.mdx

@@ -1,17 +1,8 @@
-The `updateImageTags` option expects a boolean stating if DevSpace should replace/update all image tags before deploying the project.
+If the `updateImageTags` field is set to `true` for a deployment, DevSpace will replace/update all image tags before deploying the project.
 
 When enabled, DevSpace searches all your manifests for images that are defined in the `images` section of the `devspace.yaml`. If DevSpace finds an image, it replaces or appends the image tag with the tag it created during the image building process. Image tag replacement makes sure that your application will always be started with the most up-to-date image that DevSpace has built for you.
 
-:::info In-Memory Tag Replacement
-Tag replacement takes place **in-memory** and is **not** writing anything to the filesystem, i.e. it will **never** change any of your configuration files.
-:::
-
-#### Default Value for `updateImageTags`
-```yaml
-updateImageTags: false
-```
-
-#### Example: Enable Tag Replacement
+#### Example: Enable Tag Updates
 ```yaml {3}
 deployments:
   backend:
@@ -20,3 +11,7 @@ deployments:
       manifests:
       - backend/
 ```
+
+:::info In-Memory Tag Replacement
+Tag replacement takes place **in-memory** and is **not** writing anything to the filesystem, i.e. it will **never** change any of your configuration files.
+:::

docs/pages/_partials/kustomize-options-binaryPath.mdx

@@ -1,14 +1,5 @@
 The `kustomizeArgs` option expects an array of strings stating additional arguments (and flags) that should be used when calling `kustomize build`.
 
-:::info Kustomize Deployments
-DevSpace only uses `kustomize build` to render the manifest templates. The actual deployment will be executed using `kubectl apply`.
-:::
-
-#### Default Value for `kustomizeArgs`
-```yaml
-kustomizeArgs: []
-```
-
 #### Example: Custom Kustomize Args & Flags
 ```yaml
 deployments:
@@ -23,7 +14,6 @@ deployments:
     - "--grace-period"
     - "30"
 ```
-**Explanation:**  
 Deploying the above example would roughly be equivalent to this command:
 ```bash
 kustomize build --timeout=10s --grace-period=30 -f backend/

docs/pages/_partials/kustomize-options-kustomizeArgs.mdx

@@ -1,8 +1,3 @@
 :::warning
-It is highly discouraged to run `devspace dev` multiple times in parallel because multiple instances of port forwarding and file synchronization will disturb each other. Instead:
-
-- Run `devspace enter` to open additional terminal sessions without port forwarding and file sync
-- Run `devspace logs` to start log streaming without port forwarding and file sync
-- Run `devspace sync` to sync files on-demand without starting port forwarding etc.
-- Run `devspace ui` to open the localhost development UI in the browser
+Running `devspace dev` multiple times in parallel for the <u>same project</u> does not work and returns a fatal error because multiple instances of port forwarding and file sync will disturb each other. However, running `devspace dev` for several different projects (i.e. 2 different `devspace.yaml` files with different `name`) works seamlessly.
 :::

docs/pages/_partials/warning-multiple-dev.mdx

@@ -0,0 +1,13 @@
+
+<details className="config-field" data-expandable="false" open>
+<summary>
+
+### `section` <span className="config-field-required" data-required="false">required</span> <span className="config-field-type">string</span> <span className="config-field-default"></span> <span className="config-field-enum"></span> {#commands-section}
+
+Section can be used to group similar commands together in `devspace list commands`
+
+</summary>
+
+
+
+</details>

docs/pages/configuration/_partials/v2beta1/commands/section.mdx

@@ -1,11 +1,15 @@
 
+import PartialSection from "./commands/section.mdx"
 import PartialCommand from "./commands/command.mdx"
 import PartialArgs from "./commands/args.mdx"
 import PartialAppendArgs from "./commands/appendArgs.mdx"
 import PartialDescription from "./commands/description.mdx"
 import PartialInternal from "./commands/internal.mdx"
 import PartialAfter from "./commands/after.mdx"
 
+<PartialSection />
+
+
 <PartialCommand />
 
 

docs/pages/configuration/_partials/v2beta1/commands_reference.mdx

@@ -0,0 +1,17 @@
+
+import PartialName from "./name.mdx"
+import PartialVersion from "./version.mdx"
+import PartialRepo from "./repo.mdx"
+import PartialUsername from "./username.mdx"
+import PartialPassword from "./password.mdx"
+
+<div className="group" data-group="repo">
+<div className="group-name">Source: Helm Repository</div>
+
+<PartialName />
+<PartialVersion />
+<PartialRepo />
+<PartialUsername />
+<PartialPassword />
+
+</div>