docs: rename basiscs.mdx to index.mdx

Author: LukasGentele

docs/pages/configuration/_partials/v2beta1/images/group_buildConfig.mdx

@@ -1,19 +1,19 @@
 
+import PartialDockerfile from "./dockerfile.mdx"
+import PartialContext from "./context.mdx"
 import PartialBuildArgs from "./buildArgs.mdx"
 import PartialTarget from "./target.mdx"
 import PartialNetwork from "./network.mdx"
-import PartialSkipPush from "./skipPush.mdx"
-import PartialCreatePullSecret from "./createPullSecret.mdx"
 import PartialRebuildStrategy from "./rebuildStrategy.mdx"
 
 <div className="group" data-group="buildConfig">
 <div className="group-name">Build Configuration</div>
 
+<PartialDockerfile />
+<PartialContext />
 <PartialBuildArgs />
 <PartialTarget />
 <PartialNetwork />
-<PartialSkipPush />
-<PartialCreatePullSecret />
 <PartialRebuildStrategy />
 
 </div>

docs/pages/configuration/_partials/v2beta1/images/group_pushPull.mdx

@@ -0,0 +1,11 @@
+
+import PartialSkipPush from "./skipPush.mdx"
+import PartialCreatePullSecret from "./createPullSecret.mdx"
+
+<div className="group" data-group="pushPull">
+<div className="group-name">Push & Pull</div>
+
+<PartialSkipPush />
+<PartialCreatePullSecret />
+
+</div>

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

@@ -1,10 +1,9 @@
 
 import PartialImage from "./images/image.mdx"
 import PartialTags from "./images/tags.mdx"
-import PartialDockerfile from "./images/dockerfile.mdx"
-import PartialContext from "./images/context.mdx"
-import PartialGroupoverwrites from "./images/group_overwrites.mdx"
 import PartialGroupbuildConfig from "./images/group_buildConfig.mdx"
+import PartialGroupoverwrites from "./images/group_overwrites.mdx"
+import PartialGrouppushPull from "./images/group_pushPull.mdx"
 import PartialGroupengines from "./images/group_engines.mdx"
 
 <PartialImage />
@@ -13,16 +12,13 @@ import PartialGroupengines from "./images/group_engines.mdx"
 <PartialTags />
 
 
-<PartialDockerfile />
-
-
-<PartialContext />
+<PartialGroupbuildConfig />
 
 
 <PartialGroupoverwrites />
 
 
-<PartialGroupbuildConfig />
+<PartialGrouppushPull />
 
 
 <PartialGroupengines />

…/pages/configuration/commands/basics.mdx …s/pages/configuration/commands/index.mdxdocs/pages/configuration/commands/basics.mdx renamed to docs/pages/configuration/commands/index.mdx docs/pages/configuration/commands/basics.mdx renamed to docs/pages/configuration/commands/index.mdx

@@ -135,7 +135,7 @@ deployments:
 ```
 
 ### `updateImageTags`
-The `updateImageTags` option expects a boolean stating if DevSpace should do [Image Tag Replacement](../basics.mdx#3-tag-replacement).
+The `updateImageTags` option expects a boolean stating if DevSpace should do [Image Tag Replacement](../index.mdx#3-tag-replacement).
 
 When set to `true`, DevSpace searches all your values (specified via `values` or `valuesFiles`) 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.
 
@@ -266,7 +266,7 @@ The `values` option expects an object with values that should be overriding the
 
 Compared to the `valuesFiles` option, using `values` has the following advantages:
 - It is easier to comprehend and faster to find (no references)
-- It allows you to use [dynamic config variables](../../variables/basics.mdx)
+- It allows you to use [dynamic config variables](../../variables/index.mdx)
 
 :::info
 Because both, `values` and `valuesFiles`, have advantages and disadvantages, it is often useful to combine them. When setting both, values defined in `values` have precedence over values defined in `valuesFiles`.

…es/configuration/dependencies/basics.mdx …ges/configuration/dependencies/index.mdxdocs/pages/configuration/dependencies/basics.mdx renamed to docs/pages/configuration/dependencies/index.mdx docs/pages/configuration/dependencies/basics.mdx renamed to docs/pages/configuration/dependencies/index.mdx

@@ -107,7 +107,7 @@ deployments:
 </Tabs>
 
 :::info Sequential and Concurrent Deployment
-Deployments, like images, will be processed in parallel by default. To process deployments sequentially, you can specify it as a dependency, or override the pipeline and call [create_deployments](../../configuration/pipelines/functions/create_deployments.mdx) sequentially.
+Deployments, like images, will be processed in parallel by default. To process deployments sequentially, you can specify it as a dependency, or override the pipeline and call [create_deployments](../../configuration/functions/index.mdx#create_deployments) sequentially.
 :::
 
 ## Run Deployments