🐛 Fix CI url issue

bdsoha · bdsoha · commit 5371de2f2374 · 2025-07-31T16:48:14.000+03:00
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
@@ -51,17 +51,17 @@ jobs:
         run: |
           base="https://api.github.com/repos/kloudkit/workspace/contents"
 
-          curl -sSL \
+          curl -sSfL \
             -H "Authorization: Bearer ${{ secrets.KLOUDKIT_ORG_PAT }}" \
             -H "Accept: application/vnd.github.v3.raw" \
             -o "scripts/dependencies.yaml" \
-            "${api_url}/src/build/dependencies/dependencies.yaml?ref=main"
+            "${base}/src/build/dependencies/dependencies.yaml?ref=main"
 
-          curl -sSL \
+          curl -sSfL \
             -H "Authorization: Bearer ${{ secrets.KLOUDKIT_ORG_PAT }}" \
             -H "Accept: application/vnd.github.v3.raw" \
             -o "scripts/env.reference.yaml" \
-            "${api_url}/src/env.reference.yaml?ref=main"
+            "${base}/src/rootfs/etc/workspace/env.reference.yaml?ref=main"
 
           npm run docs:generate-dynamic
 
diff --git a/.vitepress/_sidebar.ts b/.vitepress/_sidebar.ts
@@ -15,10 +15,10 @@ export default [
   {
     text: 'Editor',
     items: [
+      { text: 'Additional Features', link: '/editor/features'},
       { text: 'Authentication', link: '/editor/authentication'},
       { text: 'Aliases', link: '/editor/aliases'},
       { text: 'Extensions', link: '/editor/extensions'},
-      { text: 'Extra Features', link: '/editor/features'},
       { text: 'Port Forwarding', link: '/editor/port-forwarding'},
       { text: 'Settings', link: '/editor/settings'},
       { text: 'Storage', link: '/editor/storage'},
@@ -30,7 +30,7 @@ export default [
     text: 'Settings',
     items: [
       { text: 'Autoload Scripts', link: '/settings/autoload-scripts' },
-      { text: 'Environment Variables', link: '/settings/environment-variables' },
+      { text: 'Configuration', link: '/settings/configuration' },
       { text: 'Enterprise CA', link: '/settings/enterprise-ca' },
       { text: 'Secret Injection', link: '/settings/secrets' },
     ]
diff --git a/docs/editor/authentication.md b/docs/editor/authentication.md
@@ -17,8 +17,8 @@ Passed authentication can be easily configured by setting an environment variabl
 deploying the *workspace*.
 Setting your password is as simple as defining an `env` variable:
 
-- **`WS_PASSWORD`:** plaintext password.
-- **`WS_PASSWORD_HASHED`:** hashed passwords *(will take precedence over plaintext)*.
+- **`WS_AUTH_PASSWORD`:** plaintext password.
+- **`WS_AUTH_PASSWORD_HASHED`:** hashed passwords *(will take precedence over plaintext)*.
 
 ::: info NOTE
 All sensitive environment variables are purged before deploying Kloud Workspace, ensuring
@@ -27,7 +27,7 @@ that your password is absent from future shell sessions.
 
 ```sh{2}
 docker run \
-  -e WS_PASSWORD=super_duper_secret \
+  -e WS_AUTH_PASSWORD=super_duper_secret \
   ghcr.io/kloudkit/workspace:latest
 ```
 
@@ -45,7 +45,7 @@ Then deploy the workspace:
 
 ```sh{2}
 docker run \
-  -e WS_PASSWORD_HASHED="$argon2i$v=19$m=4096,t=3,p=1$z4DjJlJgI6S7fAdQC35ZQw$Rpu8CLMWedxJaH0eiFCetyoRbg+S8ow/RRyVCZzM6QE" \
+  -e WS_AUTH_PASSWORD_HASHED="$argon2i$v=19$m=4096,t=3,p=1$z4DjJlJgI6S7fAdQC35ZQw$Rpu8CLMWedxJaH0eiFCetyoRbg+S8ow/RRyVCZzM6QE" \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/editor/extensions.md b/docs/editor/extensions.md
@@ -36,21 +36,21 @@ Upon startup, Kloud Workspace evaluates several environment variables to automat
 installation of additional *user-defined* VSCode extensions.
 Both options below can be used in unison:
 
-- **`WS_EXTRA_VS_EXTENSIONS`:** One or more space delimited extension names.
-- **`WS_EXTRA_VS_EXTENSIONS_DIR`:** Directory of extensions with as `*.vsix`.
+- **`WS_EDITOR_ADDITIONAL_VS_EXTENSIONS`:** One or more space delimited extension names.
+- **`WS_EDITOR_ADDITIONAL_VS_EXTENSIONS_DIR`:** Directory of extensions with as `*.vsix`.
 
 ::: code-group
 
 ```sh{2} [list]
 docker run \
-  -e WS_EXTRA_VS_EXTENSIONS="dbaeumer.vscode-eslint esbenp.prettier-vscode" \
+  -e WS_EDITOR_ADDITIONAL_VS_EXTENSIONS="dbaeumer.vscode-eslint esbenp.prettier-vscode" \
   ghcr.io/kloudkit/workspace:latest
 ```
 
 ```sh{2,3} [directory]
 docker run \
-  -e WS_EXTRA_VS_EXTENSIONS_DIR=/extra-extensions \
-  -v /path/to/my-extra-extensions:/extra-extensions \
+  -e WS_EDITOR_ADDITIONAL_VS_EXTENSIONS_DIR=/additional-extensions \
+  -v /path/to/my-additional-extensions:/additional-extensions \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/editor/features.md b/docs/editor/features.md
@@ -6,7 +6,7 @@ see:
     link: /tools/apt
 ---
 
-# Extra Features
+# Additional Features
 
 Pre-installing and configuring every possible package would compromise a flexible
 *workspace* footprint.
@@ -23,12 +23,12 @@ You can choose the method that best fits your needs.
 
 ### Install at Boot
 
-Kloud Workspace evaluates the `WS_EXTRA_FEATURES` environment variable at startup to
-determine which *features* to install automatically.
+Kloud Workspace evaluates the `WS_FEATURES_ADDITIONAL_FEATURES` environment variable at
+startup to determine which *features* to install automatically.
 
 ```sh{2}
 docker run \
-  -e WS_EXTRA_FEATURES="dotnet jupyter" \
+  -e WS_FEATURES_ADDITIONAL_FEATURES="dotnet jupyter" \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/editor/port-forwarding.md b/docs/editor/port-forwarding.md
@@ -45,12 +45,12 @@ If adding DNS entries is not possible, refer to the [documentation below](#local
 a workaround you can implement on local systems.
 :::
 
-You can define the domain *(and subdomain)* structure using the `WS_PROXY_DOMAIN`
+You can define the domain *(and subdomain)* structure using the `WS_SERVER_PROXY_DOMAIN`
 environment variable:
 
 ```sh{2}
 docker run \
-  -e WS_PROXY_DOMAIN=ws.dev \
+  -e WS_SERVER_PROXY_DOMAIN=ws.dev \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/editor/terminal.md b/docs/editor/terminal.md
@@ -31,20 +31,20 @@ Some users find the descriptive prompt to be too noisy.
 To *opt-out* of some of the prompt modules, you can set any of the following environment
 `env` variables to a *truthy* value *(either `1` or `true`)*:
 
-- **`WS_PROMPT_DISABLE_DOCKER`:** Disable the `docker` module of the terminal prompt.
-- **`WS_PROMPT_DISABLE_HOSTNAME`:** Disable the `hostname` module of the terminal prompt.
-- **`WS_PROMPT_DISABLE_KUBERNETES`:** Disable the `kubernetes` module of the terminal prompt.
-- **`WS_PROMPT_DISABLE_NODEJS`:** Disable the `nodejs` module of the terminal prompt.
-- **`WS_PROMPT_DISABLE_PYTHON`:** Disable the `python` module of the terminal prompt.
-- **`WS_PROMPT_DISABLE_USER`:** Disable the user module of the terminal prompt.
+- **`WS_TERMINAL_PROMPT_HIDE_DOCKER_CONTEXT`:** Disable the `docker` module of the terminal prompt.
+- **`WS_TERMINAL_PROMPT_HIDE_HOSTNAME`:** Disable the `hostname` module of the terminal prompt.
+- **`WS_TERMINAL_PROMPT_HIDE_KUBERNETES_CONTEXT`:** Disable the `kubernetes` module of the terminal prompt.
+- **`WS_TERMINAL_PROMPT_HIDE_NODEJS_VERSION`:** Disable the `nodejs` module of the terminal prompt.
+- **`WS_TERMINAL_PROMPT_HIDE_PYTHON_VERSION`:** Disable the `python` module of the terminal prompt.
+- **`WS_TERMINAL_PROMPT_HIDE_USER`:** Disable the user module of the terminal prompt.
 
 For example, to disable the Docker and Python modules, you could add the following lines
 to your deployment:
 
 ```sh{2,3}
 docker run \
-  -e WS_PROMPT_DISABLE_DOCKER=1 \
-  -e WS_PROMPT_DISABLE_PYTHON=1 \
+  -e WS_TERMINAL_PROMPT_HIDE_DOCKER_CONTEXT=1 \
+  -e WS_TERMINAL_PROMPT_HIDE_PYTHON_VERSION=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
@@ -71,7 +71,7 @@ Tools and programming languages within the *workspace* that have corresponding
 To modify the default set of plugins, adjust the `env` variables listed below:
 
 - **`WS_ZSH_PLUGINS`:** Specifies the `zsh` plugins to be enabled in each session.
-- **`WS_ZSH_EXTRA_PLUGINS`:** Adds additional `zsh` plugins to the existing defaults.
+- **`WS_ZSH_ADDITIONAL_PLUGINS`:** Adds additional `zsh` plugins to the existing defaults.
 
 ::: code-group
 
@@ -83,7 +83,7 @@ docker run \
 
 ```sh{2} [Append]
 docker run \
-  -e WS_ZSH_EXTRA_PLUGINS="php" \
+  -e WS_ZSH_ADDITIONAL_PLUGINS="php" \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/editor/theme-and-fonts.md b/docs/editor/theme-and-fonts.md
@@ -54,12 +54,12 @@ The *Victor Mono* font is not available as a *TrueType* font.
 #### Opt-out
 
 Some users may not favor this stylistic choice.
-To disable the custom comments font, set the `WS_COMMENTS_DISABLE_FONT` environment
-variable to a *truthy* value *(either `1` or `true`)*:
+To disable the custom comments font, set the `WS_EDITOR_COMMENTS_DISABLE_FONT`
+environment variable to a *truthy* value *(either `1` or `true`)*:
 
 ```sh{2}
 docker run \
-  -e WS_COMMENTS_DISABLE_FONT=1 \
+  -e WS_EDITOR_COMMENTS_DISABLE_FONT=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/settings/autoload-scripts.md b/docs/settings/autoload-scripts.md
@@ -15,8 +15,8 @@ Therefore, in addition to the predefined entrypoint scripts, we offer the abilit
 users defined entrypoint scripts to tailor the workspace experience.
 
 ::: info TIP
-Before creating extra entrypoint scripts, ensure that the objective you intend to achieve
-is not already addressed by built-in **[extendable configuration][]**.
+Before creating additional entrypoint scripts, ensure that the objective you intend to
+achieve is not already addressed by built-in **[extendable configuration][]**.
 :::
 
 Startup scripts are defined at two levels:
diff --git a/docs/settings/configuration.md b/docs/settings/configuration.md
@@ -1,4 +1,4 @@
-# Environment Variables
+# Configuration
 
 ![Dotenv logo](/icons/dotenv.svg){.doc-image}
 
@@ -8,18 +8,21 @@ sensible defaults.
 Nearly every setting can be overridden with environment variables, giving you maximum
 flexibility.
 
-## `WS_<GROUP>` Prefix Convention
+All configuration is supplied **exclusively** through environment variables.
+No JSON, YAML, or CLI flags required. This makes the workspace fully *stateless* and
+cloud-friendly.
+
+Nearly every individual setting can still be overridden, giving you maximum flexibility.
+
+::: tip `WS_<GROUP>` Prefix Convention
 
-::: tip
 Variables that are consumed **solely** by Kloud Workspace start with `WS_<GROUP>_`
 followed by the name *(example: `WS_TERMINAL_ZSH_PLUGINS`)*.
 
-When a variable is also consumed by underlying tool, we keep its original name.
-Such variables can be reviewed in he [global variables](#global-variables) section.
+When a variable is also consumed by an underlying tool, we keep its original name.
+Such variables can be reviewed in the [global variables](#global-variables) section.
 :::
 
-## Variables
-
 <!--@include: ../partials/environment-variables.md -->
 
 ## Global Variables
diff --git a/docs/settings/enterprise-ca.md b/docs/settings/enterprise-ca.md
@@ -39,13 +39,13 @@ docker run \
 ### Install Certificate from HTTP Endpoint
 
 Alternatively, you can add your company's root CA via an *HTTP* endpoint.
-Use the `WS_EXTRA_CA_CERT_ENDPOINTS` environment variable to define one or more
+Use the `WS_CA_ADDITIONAL_CERT_ENDPOINTS` environment variable to define one or more
 *(space delimited)* endpoints pointing to the desired certificate.
 
 :::warning
 If your certificate is hosted on an insecure server you can use the
-`WS_EXTRA_CA_CERT_INSECURE` *(set to any value)* environment variable to ignore security
-checks.
+`WS_CA_ADDITIONAL_CERT_ALLOW_INSECURE` *(set to any value)* environment variable to ignore
+security checks.
 
 This may be deemed risky due to the certificate being acquired through an unsecured
 process that lacks `SSL/TLS` encryption.
@@ -57,13 +57,13 @@ Please make sure that you accept the risk.
 
 ```sh{2} [Single]
 docker run \
-  -e WS_EXTRA_CA_CERT_ENDPOINTS="http://my-company.com/shared-ca.pem" \
+  -e WS_CA_ADDITIONAL_CERT_ENDPOINTS="http://comp.me/shared-ca.pem" \
   ghcr.io/kloudkit/workspace
 ```
 
 ```sh{2} [Multiple]
 docker run \
-  -e WS_EXTRA_CA_CERT_ENDPOINTS="http://my-company.com/shared-1.pem http://other.com/ca.pem" \
+  -e WS_CA_ADDITIONAL_CERT_ENDPOINTS="http://comp.me/share-1.pem http://other.me/ca.pem" \
   ghcr.io/kloudkit/workspace
 ```
 
diff --git a/docs/tools/apt.md b/docs/tools/apt.md
@@ -18,7 +18,7 @@ installations, and prevent the overwriting of user-defined files.
 
 By default, Kloud Workspace is set up with a range of additional repository sources
 alongside the standard ones.
-All extra sources are signed with `gpg` keys to ensure secure and verified package
+All additional sources are signed with `gpg` keys to ensure secure and verified package
 installations.
 
 ### Disabling Sources
@@ -42,7 +42,7 @@ docker run \
 
 ### Update Repository Cache
 
-You can optionally trigger a package cache update by setting the `WS_APT_UPDATE_REPOS`
+You can optionally trigger a package cache update by setting the `WS_APT_UPDATE_CACHE`
 environment variable to a *truthy* value *(`1` or `true`)*.
 
 Update will occur after adding custom sources to ensures that any newly added
@@ -86,7 +86,7 @@ We recommend reviewing the available features before opting for manual package i
 ## Additional GPG Keys
 
 Some third-party repositories require you to trust their signing key.
-Provide extra keys with **`WS_APT_ADDITIONAL_GPG_KEYS`** as one or more
+Provide additional keys with **`WS_APT_ADDITIONAL_GPG_KEYS`** as one or more
 space-delimited `name:url` pairs.
 
 Each key is downloaded at startup and stored in `/etc/apt/keyrings/<name>.gpg`.
diff --git a/docs/tools/docker.md b/docs/tools/docker.md
@@ -65,7 +65,7 @@ Once `sysbox` is installed, run the workspace using the `sysbox-runc` runtime:
 ```sh{2,3}
 docker run \
   --runtime=sysbox-runc \
-  -e WS_CONFIGURE_DOCKER=1 \
+  -e WS_DOCKER_ENABLE_CLIENT=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
@@ -78,7 +78,7 @@ However, this requires the container to run in **privileged** mode:
 ```sh{2,3}
 docker run \
   --privileged \
-  -e WS_CONFIGURE_DOCKER=1 \
+  -e WS_DOCKER_ENABLE_CLIENT=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
@@ -89,7 +89,7 @@ docker run \
 ```sh{2,3}
 docker run \
   -v /var/run/docker.sock:/var/run/docker.sock:ro \
-  -e WS_CONFIGURE_DOCKER=1 \
+  -e WS_DOCKER_ENABLE_CLIENT=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
@@ -174,12 +174,12 @@ permissions for interacting with the Docker socket.
 In certain instances *(specifically, `#1` and`#2`)*, the daemon may not be running upon
 startup.
 
-To speed up the process, during initialization, assign the `WS_CONFIGURE_DOCKER`
+To speed up the process, during initialization, assign the `WS_DOCKER_ENABLE_CLIENT`
 environment variable to effortlessly initiate the daemon *(if necessary)*:
 
 ```sh{2}
 docker run \
-  -e WS_CONFIGURE_DOCKER=1 \
+  -e WS_DOCKER_ENABLE_CLIENT=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
@@ -198,7 +198,7 @@ container, ensuring the container has the appropriate permissions, as seen below
 docker run \
   --group-add=8888
   -v /var/run/docker.sock:/var/run/docker.sock:ro \
-  -e WS_CONFIGURE_DOCKER=1 \
+  -e WS_DOCKER_ENABLE_CLIENT=1 \
   ghcr.io/kloudkit/workspace:latest
 ```
 
diff --git a/docs/tools/git.md b/docs/tools/git.md
@@ -64,7 +64,7 @@ repository during startup.
 Common use cases include *CI*, short-lived instances used during integration testing, or
 environments in the cloud where persistent volumes are costly or impractical.
 
-To facilitate this, you can provide the environment variable `WS_CLONE_WORKSPACE_REPO`.
+To facilitate this, you can provide the environment variable `WS_GIT_CLONE_REPO`.
 If specified, the *workspace* will clone the repository into `WS_ROOT`
 *(default: `/workspace`)* if the directory is empty.
 
diff --git a/docs/tools/helm.md b/docs/tools/helm.md
@@ -28,14 +28,14 @@ To retain these configurations across workspace restarts or updates:
   Mounting a volume or bind-mount to this location ensures your repositories,
   credentials, and related files remain intact even if the container is re-created.
 
-2. **Use the `WS_CONFIGURE_HELM` Environment Variable:**
+2. **Use the `WS_HELM_PRELOAD_CACHE` Environment Variable:**
   You can streamline the process of autoloading HELM’s repository cache by setting the
-  `WS_CONFIGURE_HELM` environment variable.
+  `WS_HELM_PRELOAD_CACHE` environment variable.
   This causes the workspace to automatically load your cached repos whenever it starts.
 
 ```sh
 docker run \
-  -e WS_CONFIGURE_HELM=1 \
+  -e WS_HELM_PRELOAD_CACHE=1 \
   -v helm:/home/kloud/.config/helm \
   ghcr.io/kloudkit/workspace:latest
 ```
diff --git a/docs/tools/python.md b/docs/tools/python.md
@@ -78,8 +78,8 @@ pip install ipython
 Kloud Workspace already includes a custom IPython profile *(`/etc/ipython/ipython_config`)* whose
 prompt colors and syntax‑highlighting align with the Kloud Workspace's overall theme.
 
-Once IPython is installed it will pick up these settings automatically—no extra configuration
-required.
+Once IPython is installed it will pick up these settings automatically—no additional
+configuration required.
 
 [Pylance]: https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance
 [Jedi Language Server]: https://github.com/pappasam/jedi-language-server
diff --git a/scripts/create-dependencies-docs.mjs b/scripts/create-dependencies-docs.mjs
diff --git a/scripts/create-env-reference-docs.mjs b/scripts/create-env-reference-docs.mjs
