deno yaml changes + init -> initCommands

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

@@ -65,7 +65,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Bun application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Bun application start command

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

@@ -32,19 +32,17 @@ zerops:
 
       # REQUIRED. Build your application
       buildCommands:
-        - npm i
-        - npm run build
+        - deno task build
 
       # REQUIRED. Select which files / folders to deploy after
       # the build has successfully finished
       deployFiles:
         - dist
-        - package.json
-        - node_modules
+        - deno.jsonc
 
       # OPTIONAL. Which files / folders you want to cache for the next build.
       # Next builds will be faster when the cache is used.
-      cache: node_modules
+      # cache: directory
 
     # ==== how to run your application ====
     run:
@@ -65,11 +63,11 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Deno application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Deno application start command
-      start: npm start
+      start: deno task start
 ```
 
 The top-level element is always `zerops`.
@@ -247,8 +245,7 @@ zerops:
 
       # REQUIRED. Build your application
       buildCommands:
-        - npm i
-        - npm run build
+        - deno task build
       ...
 ```
 
@@ -267,8 +264,8 @@ Use following syntax to run all commands in the same environment context. For ex
 ```yml
 buildCommands:
   - |
-    npm i
-    npm run build
+    deno test
+    deno task build
 ```
 
 #### Run build commands as a separate shell instances
@@ -277,8 +274,7 @@ When the following syntax is used, each command is triggered in a separate envir
 
 ```yml
 buildCommands:
-  - npm i
-  - npm run build
+  - deno task build
 ```
 
 #### Command exit code
@@ -682,10 +678,10 @@ zerops:
     # ==== how to run your application ====
     run:
       # REQUIRED. Your Deno application start command
-      start: npm start
+      start: deno task start
 ```
 
-We recommend starting your Deno application using `npm start`.
+We recommend starting your Deno application using `deno task start`.
 
 ### health check
 
@@ -718,7 +714,7 @@ zerops:
     # ==== how to run your application ====
     run:
       # REQUIRED. Your Deno application start command
-      start: npm start
+      start: deno task start
 
       # OPTIONAL. Define a health check with a HTTP GET request option.
       # Configures the check on http://127.0.0.1:80/status
@@ -751,7 +747,7 @@ zerops:
     # ==== how to run your application ====
     run:
       # REQUIRED. Your Deno application start command
-      start: npm start
+      start: deno task start
 
       # OPTIONAL. Define a health check with a shell command.
       healthCheck:

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

@@ -66,7 +66,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your .NET application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your .NET application start command

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

@@ -63,7 +63,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Elixir application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Elixir application start command

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

@@ -65,7 +65,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Gleam application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Gleam application start command

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

@@ -60,7 +60,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Go application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Go application start command

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

@@ -60,7 +60,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Java application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Java application start command

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

@@ -77,7 +77,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Nginx application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # OPTIONAL. Customise the folder that will be used as the root of the publicly

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

@@ -65,7 +65,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Node.js application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Node.js application start command

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

@@ -58,7 +58,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your PHP application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # OPTIONAL. Customise the folder that will be used as the root of the publicly

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

@@ -61,7 +61,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Python application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Python application start command

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

@@ -62,7 +62,7 @@ zerops:
       # OPTIONAL. Run one or more commands each time a new runtime container
       # is started or restarted. These commands are triggered before
       # your Rust application is started.
-      # init:
+      # initCommands:
       #  - rm -rf ./cache
 
       # REQUIRED. Your Rust application start command