updates

apps/docs/content/alpine/how-to/build-pipeline.mdx

@@ -183,7 +183,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -216,7 +216,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -526,6 +526,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](/alpine/how-to/logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -598,6 +602,10 @@ zerops:
 
 These commands are triggered in the runtime container before your Alpine application is started via the [start command](#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution

apps/docs/content/alpine/how-to/build-process.mdx

@@ -58,7 +58,7 @@ The default <Var name="serviceDisplay" /> build environment contains:
 To install additional packages or tools, add one or more <VarLink name="servicePath" path="/{{VAR}}/how-to/build-pipeline#preparecommands">build.prepareCommands</VarLink> to your `zerops.yaml`.
 
 :::info
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in the `/build/source` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
 :::
 
 ### Build hardware resources

apps/docs/content/bun/how-to/build-pipeline.mdx

@@ -219,7 +219,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -253,7 +253,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -572,6 +572,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](build-pipeline#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -645,6 +649,10 @@ zerops:
 
 These commands are triggered in the runtime container before your Bun application is started via the [start command](build-pipeline#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution

apps/docs/content/deno/how-to/build-pipeline.mdx

@@ -214,7 +214,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -247,7 +247,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -565,6 +565,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](/deno/how-to/logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -638,6 +642,10 @@ zerops:
 
 These commands are triggered in the runtime container before your Deno application is started via the [start command](#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution

apps/docs/content/deno/how-to/build-process.mdx

@@ -47,7 +47,7 @@ The default Deno build environment contains:
 To install additional packages or tools, add one or more [build.prepareCommands](/deno/how-to/build-pipeline#preparecommands) to your `zerops.yaml`.
 
 :::info
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in the `/build/source` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
 :::
 
 ### Build hardware resources

apps/docs/content/dotnet/how-to/build-pipeline.mdx

@@ -218,7 +218,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -251,7 +251,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -585,6 +585,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](/dotnet/how-to/logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -660,6 +664,10 @@ zerops:
 
 These commands are triggered in the runtime container before your .NET application is started via the [start command](#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution

apps/docs/content/elixir/how-to/build-pipeline.mdx

@@ -215,7 +215,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -249,7 +249,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -568,6 +568,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](/elixir/how-to/logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -641,6 +645,10 @@ zerops:
 
 These commands are triggered in the runtime container before your Elixir application is started via the [start command](#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution

apps/docs/content/features/pipeline.mdx

@@ -252,6 +252,10 @@ run:
     - sudo apt-get update && apt-get install -y some-package  # for Ubuntu
 ```
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 Zerops creates the custom runtime image from this container after all commands complete successfully.
 
 #### `build.addToRunPrepare`

apps/docs/content/gleam/how-to/build-pipeline.mdx

@@ -216,7 +216,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -250,7 +250,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -569,6 +569,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](/gleam/how-to/logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -642,6 +646,10 @@ zerops:
 
 These commands are triggered in the runtime container before your Gleam application is started via the [start command](#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution

apps/docs/content/go/how-to/build-pipeline.mdx

@@ -212,7 +212,7 @@ When the first build is triggered, Zerops will
 2. download your application code from your repository
 3. run the prepare commands in the defined order
 
-The application code is available in the `/var/www` folder in your build container before the prepare commands are triggered. This allows you to use any file from your application code in your prepare commands (e.g. a configuration file).
+The application code is available in `/build/source` before the prepare commands are triggered, so you can use any file from your repository in your prepare commands (e.g. a configuration file). The commands themselves run in the `/home/zerops` directory.
 
 :::note
 These commands are skipped when using cached environment. Modifying `prepareCommands` will invalidate your build cache. See our [Build Cache Documentation](/features/build-cache) for details about cache invalidation.
@@ -245,7 +245,7 @@ zerops:
       ...
 ```
 
-Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container.
+Build commands are optional. Zerops triggers each command in the defined order in a dedicated build container, running from the `/build/source` directory.
 
 Before the build commands are triggered the build container contains:
 
@@ -579,6 +579,10 @@ When the first deploy with a defined prepare attribute is triggered, Zerops will
 2. optionally: [copy selected folders or files from your build container](#copy-folders-or-files-from-your-build-container)
 3. run the `prepareCommands` commands in the defined order
 
+:::note
+`run.prepareCommands` run in the `/home/zerops` directory.
+:::
+
 #### Command exit code
 
 If any command fails, it returns an exit code other than 0 and the deploy is canceled. Read the [prepare runtime log](/go/how-to/logs#prepare-runtime-log) to troubleshoot the error. If the command ends successfully, it returns the exit code 0 and Zerops triggers the following command. When all `prepareCommands` commands are finished, your custom runtime environment is ready for the deploy phase.
@@ -652,6 +656,10 @@ zerops:
 
 These commands are triggered in the runtime container before your Go application is started via the [start command](#start).
 
+:::note
+`run.initCommands` run in the `/var/www` directory.
+:::
+
 Use init commands to clean or initialise your application cache or similar operations.
 
 :::caution