Developer first page

apps/docs/.content.eslintrc.js

@@ -1,4 +1,9 @@
 module.exports = {
   root: true,
   extends: ['docs/content'],
+  rules: {
+    'quotes': ['error', 'single'],
+    'semi': ['error', 'always'],
+    'max-len': ['error', { code: 80, ignoreComments: true }]
+  }
 };

apps/docs/content/bun/how-to/access.mdx

@@ -55,12 +55,12 @@ Use the <a href="/references/ssh">`ssh` command</a> to connect to your service v
 
 ## Public access through zerops.io subdomain
 
-By default, your Bun service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Bun service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
 
 ## Public access through your domain
 
 By default, your Bun service is not publicly accessible. When your application is ready for production or if you want to test it on the production domain, [configure the public access through your domain](/features/access#public-access-through-your-domain).
 
 ## Public access from another Zerops project
 
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](bun/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](bun/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).

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

@@ -9,11 +9,11 @@ import UnorderedCodeList from 'docs/src/components/UnorderedCodeList';
 
 Zerops provides a customizable build and runtime environment for your Bun application.
 
-## Add zerops.yml to your repository
+## Add zerops.yaml to your repository
 
-Start by adding `zerops.yml` file to the **root of your repository** and modify it to fit your application:
+Start by adding `zerops.yaml` file to the **root of your repository** and modify it to fit your application:
 
-```yml
+```yaml
 zerops:
   # define hostname of your service
   - setup: app
@@ -78,9 +78,9 @@ The top-level element is always `zerops`.
 ### Setup
 
 The first element `setup` contains the **hostname** of your service. A runtime service with the same hostname must exist in Zerops.
-Zerops supports the definition of multiple runtime services in a single `zerops.yml`. This is useful when you use a monorepo. Just add multiple setup elements in your `zerops.yml`:
+Zerops supports the definition of multiple runtime services in a single `zerops.yaml`. This is useful when you use a monorepo. Just add multiple setup elements in your `zerops.yaml`:
 
-```yml
+```yaml
 zerops:
   # definition for app service
   - setup: app
@@ -105,7 +105,7 @@ Following options are available for Bun builds:
 
 <UnorderedCodeList data={data.bun.base} />
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -124,12 +124,12 @@ zerops:
 </p>
 
 :::info
-You can change the base environment when you need to. Just simply modify the `zerops.yml` in your repository.
+You can change the base environment when you need to. Just simply modify the `zerops.yaml` in your repository.
 :::
 
 If you need to install more technologies to the build environment, set multiple values as a yaml array. For example:
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -143,7 +143,7 @@ zerops:
       ...
 ```
 
-See the full list of supported [build base environments](/zerops-yml/base-list#runtime-services).
+See the full list of supported [build base environments](/zerops-yaml/base-list#runtime-services).
 
 To customise your build environment use the [prepareCommands](bun/how-to/build-pipeline#preparecommands) attribute.
 
@@ -188,7 +188,7 @@ The base build environment contains:
 
 To install additional packages or tools add one or more prepare commands:
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -229,7 +229,7 @@ You can configure your prepare commands to be run in a single shell instance or
 
 _REQUIRED._ Defines build commands.
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -257,7 +257,7 @@ Before the build commands are triggered the build container contains:
 
 Use following syntax to run all commands in the same environment context. For example, if one command changes the current directory, the next command continues in that directory. When one command creates an environment variable, the next command can access it.
 
-```yml
+```yaml
 buildCommands:
   - |
     bun i
@@ -268,7 +268,7 @@ buildCommands:
 
 When the following syntax is used, each command is triggered in a separate environment context. For example, each shell instance starts in the home directory again. When one command creates an environment variable, it won't be available for the next command.
 
-```yml
+```yaml
 buildCommands:
   - bun i
   - bun run build
@@ -278,7 +278,7 @@ buildCommands:
 
 If any command fails, it returns an exit code other than 0 and the build is canceled. Read the [build log](bun/how-to/logs#build-log) to troubleshoot the error. If the error log doesn't contain any specific error message, try to run your build with the --verbose option.
 
-```yml
+```yaml
 buildCommands:
   - bun i --verbose
   - bun run build
@@ -290,7 +290,7 @@ If the command ends successfully, it returns the exit code 0 and Zerops triggers
 
 _REQUIRED._ Selects which files or folders will be deployed after the build has successfully finished. To filter out specific files or folders, use <a href="#deployignore">`.deployignore`</a> file.
 
-```yml
+```yaml
 # REQUIRED. Select which files / folders to deploy after
 # the build has successfully finished
 deployFiles:
@@ -301,29 +301,29 @@ deployFiles:
 
 Determines files or folders produced by your build, which should be deployed to your runtime service containers.
 
-The path starts from the **root directory** of your project (the location of `zerops.yml`). You must enclose the name in quotes if the folder or the file name contains a space.
+The path starts from the **root directory** of your project (the location of `zerops.yaml`). You must enclose the name in quotes if the folder or the file name contains a space.
 
 The files/folders will be placed into `/var/www` folder in runtime, e.g. `./src/assets/fonts` would result in `/var/www/src/assets/fonts`.
 
 #### Examples
 
 Deploys a folder, and a file from the project root directory:
 
-```yml
+```yaml
 deployFiles:
   - dist
   - package.json
 ```
 
 Deploys the whole content of the build container:
 
-```yml
+```yaml
 deployFiles: .
 ```
 
 Deploys a folder, and a file in a defined path:
 
-```yml
+```yaml
 deployFiles:
   - ./path/to/file.txt
   - ./path/to/dir/
@@ -335,19 +335,19 @@ Zerops supports the `~` character as a wildcard for one or more folders in the p
 
 Deploys all `file.txt` files that are located in any path that begins with `/path/` and ends with `/to/`
 
-```yml
+```yaml
 deployFiles: ./path/~/to/file.txt
 ```
 
 Deploys all folders that are located in any path that begins with `/path/to/`
 
-```yml
+```yaml
 deployFiles: ./path/to/~/
 ```
 
 Deploys all folders that are located in any path that begins with `/path/` and ends with `/to/`
 
-```yml
+```yaml
 deployFiles: ./path/~/to/
 ```
 
@@ -366,7 +366,7 @@ For consistency, it's recommended to configure both your `.gitignore` and `.depl
 
 Examples:
 
-```yml title="zerops.yml"
+```yaml title="zerops.yaml"
 zerops:
   - setup: app
     build:
@@ -393,7 +393,7 @@ This example above ignores `file.txt` in ANY directory named `src`, such as:
 
 _OPTIONAL._ Defines which files or folders will be cached for the next build.
 
-```yml
+```yaml
 # OPTIONAL. Which files / folders you want to cache for the next build.
 # Next builds will be faster when the cache is used.
 cache: file.txt
@@ -411,7 +411,7 @@ _OPTIONAL._ Defines the environment variables for the build environment.
 
 Enter one or more env variables in following format:
 
-```yml
+```yaml
 zerops:
   # define hostname of your service
   - setup: app
@@ -442,7 +442,7 @@ Following options are available for Bun runtimes:
 
 <UnorderedCodeList data={data.bun.base} />
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -465,12 +465,12 @@ zerops:
 </p>
 
 :::info
-You can change the base environment when you need to. Just simply modify the `zerops.yml` in your repository.
+You can change the base environment when you need to. Just simply modify the `zerops.yaml` in your repository.
 :::
 
 If you need to install more technologies to the runtime environment, set multiple values as a yaml array. For example:
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -490,7 +490,7 @@ zerops:
       ...
 ```
 
-See the full list of supported [run base environments](/zerops-yml/base-list).
+See the full list of supported [run base environments](/zerops-yaml/base-list).
 
 To customise your build environment use the `prepareCommands` attribute.
 
@@ -540,7 +540,7 @@ _OPTIONAL._ Customises the Bun runtime environment by installing additional depe
   additional packages or tools add one or more prepare commands:
 </p>
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -594,14 +594,14 @@ You can configure your prepare commands to be run in a single shell instance or
 
 The prepare runtime container does not contain your application code nor the built application. If you need to copy some folders or files from the build container to the runtime container (e.g. a configuration file) use the `addToRunPrepare` attribute in the [build section](#build-pipeline-configuration).
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
     # ==== how to build your application ====
     build:
       ...
-      addToRunPrepare: ./runtime-config.yml
+      addToRunPrepare: ./runtime-config.yaml
 
     # ==== how to run your application ====
     run:
@@ -613,13 +613,13 @@ zerops:
       ...
 ```
 
-In the example above Zerops will copy the `runtime-config.yml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered.
+In the example above Zerops will copy the `runtime-config.yaml` file from your build container **after the build has finished** into the new **prepare runtime** container. The copied files and folders will be available in the `xxx` folder in the new prepare runtime container before the prepare commands are triggered.
 
 ### initCommands
 
 _OPTIONAL._ Defines one or more commands to be run each time a new runtime container is started or a container is restarted.
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -659,7 +659,7 @@ _OPTIONAL._ Defines the environment variables for the runtime environment.
 
 Enter one or more env variables in following format:
 
-```yml
+```yaml
 zerops:
   # define hostname of your service
   - setup: app
@@ -680,7 +680,7 @@ Read more about [environment variables](bun/how-to/env-variables) in Zerops.
 
 _REQUIRED._ Defines the start command for your Bun application.
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -716,7 +716,7 @@ Following attributes are available:
 
 **Example:**
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -749,7 +749,7 @@ Following attributes are available:
 
 **Example:**
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -778,7 +778,7 @@ _OPTIONAL._ Defines cron jobs.
 
 Setup cron jobs in the following format:
 
-```yml
+```yaml
 zerops:
   # define hostname of your service
   - setup: app
@@ -817,7 +817,7 @@ Following attributes are available:
 
 **Example:**
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app
@@ -850,7 +850,7 @@ Following attributes are available:
 
 **Example:**
 
-```yml
+```yaml
 zerops:
   # hostname of your service
   - setup: app

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

@@ -54,11 +54,11 @@ The build cancellation is available before the build pipeline is finished. When
 The default Bun build environment contains:
 
 - <span>{data.alpine.default}</span>
-- selected version of Bun defined in `zerops.yml` [build.base](bun/how-to/build-pipeline#base) parameter
+- selected version of Bun defined in `zerops.yaml` [build.base](bun/how-to/build-pipeline#base) parameter
 - [zCLI](/references/cli), Zerops command line tool
 - `npm`, `yarn`, `git` and `npx` tools
 
-If you prefer the Ubuntu OS instead of Alpine, set the [build.os](/bun/how-to/build-pipeline#os) attribute to `ubuntu`. To install additional packages or tools add one or more [build.prepareCommands](bun/how-to/build-pipeline#preparecommands) commands to your `zerops.yml`.
+If you prefer the Ubuntu OS instead of Alpine, set the [build.os](/bun/how-to/build-pipeline#os) attribute to `ubuntu`. To install additional packages or tools add one or more [build.prepareCommands](bun/how-to/build-pipeline#preparecommands) commands 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).
@@ -104,7 +104,7 @@ This will force Zerops to run the next build clean, including all prepare comman
 
 If any [build command](bun/how-to/build-pipeline#buildcommands) fails, it returns an exit code other than 0 and the build is canceled. Read the [build log](bun/how-to/logs#build-log) to troubleshoot the error. If the error log doesn't contain any specific error message, try to run your build with the `--verbose` option.
 
-```yml
+```yaml
 buildCommands:
   - npm i --verbose
   - npm run build