Merge remote-tracking branch 'origin/master' into issue_3265_fix_files_in_place_update

Author: un-def

.github/workflows/build-docs.yml

@@ -2,10 +2,6 @@ name: Build Docs
 
 on:
   workflow_call:
-    inputs:
-      release-tag:
-        type: string
-        required: false
 
 jobs:
   build-docs:
@@ -17,18 +13,10 @@ jobs:
           python-version: 3.11
       - name: Install dstack
         run: |
-          uv pip install examples/plugins/example_plugin_server
-          if [ -n "${{ inputs.release-tag }}" ]; then
-            uv pip install "dstack[server]==${{ inputs.release-tag }}"
-          else
-            uv pip install -e '.[server]'
-          fi
+          uv sync --extra server
       - name: Build
         run: |
-          uv pip install pillow cairosvg
           sudo apt-get update && sudo apt-get install -y libcairo2-dev libfreetype6-dev libffi-dev libjpeg-dev libpng-dev libz-dev
-          uv pip install mkdocs-material "mkdocs-material[imaging]" mkdocs-material-extensions mkdocs-redirects mkdocs-gen-files "mkdocstrings[python]" mkdocs-render-swagger-plugin --upgrade
-          uv pip install git+https://${{ secrets.GH_TOKEN }}@github.com/squidfunk/mkdocs-material-insiders.git
           uv run mkdocs build -s
       - uses: actions/upload-artifact@v4
         with:

.github/workflows/docs.yaml

@@ -2,15 +2,10 @@ name: Build & Deploy Docs
 
 on:
   workflow_dispatch:
-    inputs:
-      release-tag:
-        description: "dstack version"
 
 jobs:
   build-docs:
     uses: ./.github/workflows/build-docs.yml
-    with:
-      release-tag: ${{ inputs.release-tag }}
     secrets: inherit
 
   deploy-docs:

README.md

@@ -52,7 +52,7 @@ Backends can be set up in `~/.dstack/server/config.yml` or through the [project
 
 For more details, see [Backends](https://dstack.ai/docs/concepts/backends).
 
-> When using `dstack` with on-prem servers, backend configuration isn’t required. Simply create [SSH fleets](https://dstack.ai/docs/concepts/fleets#ssh) once the server is up.
+> When using `dstack` with on-prem servers, backend configuration isn’t required. Simply create [SSH fleets](https://dstack.ai/docs/concepts/fleets#ssh-fleets) once the server is up.
 
 ##### Start the server
 

contributing/DEVELOPMENT.md

@@ -48,3 +48,7 @@ pyright -p .
 ## 6. Frontend
 
 See [FRONTEND.md](FRONTEND.md) for the details on how to build and develop the frontend.
+
+## 7. Documentation
+
+See [DOCS.md](DOCS.md) for the details on how to preview or build the documentation.

contributing/DOCS.md

@@ -0,0 +1,49 @@
+# Documentation setup
+
+## 1. Clone the repo:
+
+```shell
+git clone https://github.com/dstackai/dstack
+cd dstack
+```
+
+## 2. Install uv:
+
+https://docs.astral.sh/uv/getting-started/installation
+
+```shell
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+## 3. Install `dstack` with all extras and dev dependencies:
+
+> [!WARNING]
+> Building documentation requires `python_version >= 3.11`.
+
+```shell
+uv sync --all-extras
+```
+
+`dstack` will be installed into the project's `.venv` in editable mode.
+
+## 4. (Recommended) Install pre-commit hooks:
+
+Code formatting and linting can be done automatically on each commit with `pre-commit` hooks:
+
+```shell
+uv run pre-commit install
+```
+
+## 5. Preview documentation
+
+To preview the documentation, run the follow command:
+
+```shell
+uv run mkdocs serve -w examples -s
+```
+
+If you want to build static files, you can use the following command:
+
+```shell
+uv run mkdocs build -s
+```

docker/server/entrypoint.sh

@@ -10,7 +10,7 @@ fi
 DB_PATH="${HOME}/.dstack/server/data/sqlite.db"
 mkdir -p "$(dirname "$DB_PATH")"
 if [[ -z "${LITESTREAM_REPLICA_URL}" ]]; then
-  exec dstack server --host 0.0.0.0
+  dstack server --host 0.0.0.0
 else
   if [[ ! -f "$DB_PATH" ]]; then
     echo "Attempting Litestream restore..."
@@ -23,5 +23,5 @@ else
       fi
     fi
   fi
-  exec litestream replicate -exec "dstack server --host 0.0.0.0" "$DB_PATH" "$LITESTREAM_REPLICA_URL"
+  litestream replicate -exec "dstack server --host 0.0.0.0" "$DB_PATH" "$LITESTREAM_REPLICA_URL"
 fi

docs/blog/posts/amd-on-tensorwave.md

@@ -15,7 +15,7 @@ to orchestrate AI containers with any AI cloud vendor, whether they provide on-d
 
 In this tutorial, we’ll walk you through how `dstack` can be used with
 [TensorWave :material-arrow-top-right-thin:{ .external }](https://tensorwave.com/){:target="_blank"} using
-[SSH fleets](../../docs/concepts/fleets.md#ssh).
+[SSH fleets](../../docs/concepts/fleets.md#ssh-fleets).
 
 <img src="https://dstack.ai/static-assets/static-assets/images/dstack-tensorwave-v2.png" width="630"/>
 
@@ -235,6 +235,6 @@ Want to see how it works? Check out the video below:
 <iframe width="750" height="520" src="https://www.youtube.com/embed/b1vAgm5fCfE?si=qw2gYHkMjERohdad&rel=0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
 !!! info "What's next?"
-    1. See [SSH fleets](../../docs/concepts/fleets.md#ssh)
+    1. See [SSH fleets](../../docs/concepts/fleets.md#ssh-fleets)
     2. Read about [dev environments](../../docs/concepts/dev-environments.md), [tasks](../../docs/concepts/tasks.md), and [services](../../docs/concepts/services.md)
     3. Join [Discord :material-arrow-top-right-thin:{ .external }](https://discord.gg/u8SmfwPpMd)

docs/blog/posts/benchmark-amd-containers-and-partitions.md

@@ -122,7 +122,7 @@ The full, reproducible steps are available in our GitHub repository. Below is a
 
 #### Creating a fleet
 
-We first defined a `dstack` [SSH fleet](../../docs/concepts/fleets.md#ssh) to manage the two-node cluster.
+We first defined a `dstack` [SSH fleet](../../docs/concepts/fleets.md#ssh-fleets) to manage the two-node cluster.
 
 ```yaml
 type: fleet

docs/blog/posts/gh200-on-lambda.md

@@ -11,7 +11,7 @@ categories:
 # Supporting ARM and NVIDIA GH200 on Lambda
 
 The latest update to `dstack` introduces support for NVIDIA GH200 instances on [Lambda](../../docs/concepts/backends.md#lambda)
-and enables ARM-powered hosts, including GH200 and GB200, with [SSH fleets](../../docs/concepts/fleets.md#ssh).
+and enables ARM-powered hosts, including GH200 and GB200, with [SSH fleets](../../docs/concepts/fleets.md#ssh-fleets).
 
 <img src="https://dstack.ai/static-assets/static-assets/images/dstack-arm--gh200-lambda-min.png" width="630"/>
 
@@ -78,7 +78,7 @@ $ dstack apply -f .dstack.yml
 !!! info "Retry policy"
     Note, if GH200s are not  available at the moment, you can specify the [retry policy](../../docs/concepts/dev-environments.md#retry-policy) in your run configuration so that `dstack` can run the configuration once the GPU becomes available.
 
-> If you have GH200 or GB200-powered hosts already provisioned via Lambda, another cloud provider, or on-prem, you can now use them with [SSH fleets](../../docs/concepts/fleets.md#ssh).
+> If you have GH200 or GB200-powered hosts already provisioned via Lambda, another cloud provider, or on-prem, you can now use them with [SSH fleets](../../docs/concepts/fleets.md#ssh-fleets).
 
 !!! info "What's next?"
     1. Sign up with [Lambda :material-arrow-top-right-thin:{ .external }](https://cloud.lambda.ai/sign-up?_gl=1*1qovk06*_gcl_au*MTg2MDc3OTAyOS4xNzQyOTA3Nzc0LjE3NDkwNTYzNTYuMTc0NTQxOTE2MS4xNzQ1NDE5MTYw*_ga*MTE2NDM5MzI0My4xNzQyOTA3Nzc0*_ga_43EZT1FM6Q*czE3NDY3MTczOTYkbzM0JGcxJHQxNzQ2NzE4MDU2JGo1NyRsMCRoMTU0Mzg1NTU1OQ..){:target="_blank"}

docs/blog/posts/gpu-health-checks.md

@@ -55,7 +55,7 @@ For active checks today, you can run [NCCL tests](../../examples/clusters/nccl-t
 
 ## Supported backends
 
-Passive GPU health checks work on AWS (except with custom `os_images`), Azure (except A10 GPUs), GCP, OCI, and [SSH fleets](../../docs/concepts/fleets.md#ssh) where DCGM is installed and configured for background checks. 
+Passive GPU health checks work on AWS (except with custom `os_images`), Azure (except A10 GPUs), GCP, OCI, and [SSH fleets](../../docs/concepts/fleets.md#ssh-fleets) where DCGM is installed and configured for background checks. 
 
 > Fleets created before version 0.19.22 need to be recreated to enable this feature.