diff --git a/docs/content/Deploying/Pip-Install.mdx b/docs/content/Deploying/Pip-Install.mdx index 84358c96..43dbf33c 100644 --- a/docs/content/Deploying/Pip-Install.mdx +++ b/docs/content/Deploying/Pip-Install.mdx @@ -41,7 +41,11 @@ pip install --index-url https://download.pytorch.org/whl/cpu torch torchvision pip install "docsgpt[docling]" ``` -`uv pip install` accepts the same two commands. With `pipx`, install `docsgpt[docling]` and then run `pipx inject --index-url https://download.pytorch.org/whl/cpu docsgpt torch torchvision` to swap the CUDA build for the CPU one. +`uv pip install` accepts the same two commands. With `pipx`, install `docsgpt[docling]` first, then replace the CUDA build inside its environment (`--no-deps` keeps pip from touching torch's dependencies, which the PyTorch index carries in older copies): + +```bash +pipx runpip docsgpt install --force-reinstall --no-deps --index-url https://download.pytorch.org/whl/cpu torch torchvision +``` ## Configure diff --git a/docs/content/upgrading.mdx b/docs/content/upgrading.mdx index abf71d2c..e00029a5 100644 --- a/docs/content/upgrading.mdx +++ b/docs/content/upgrading.mdx @@ -111,6 +111,16 @@ alias, so nothing breaks on upgrade, but update these before the alias goes: than it would have (a monthly sync by up to a month). Nothing to do. - Data directories do not move: the compose files keep your indexes, inputs and vectors under `application/` in the checkout, where they already are. +- The backend is also a package now (`pip install docsgpt`, see + [Install with pip](/Deploying/Pip-Install)). Runtime data lives in a data + home: `DOCSGPT_HOME`, else the checkout, else the directory the process + starts in. One consequence for a source checkout: the embedded Milvus + (`MILVUS_URI`) and LanceDB (`LANCEDB_PATH`) default paths now resolve under + the checkout instead of the start directory. If you use either store at its + default path and start DocsGPT from another directory, the old data is at + `/milvus_local.db` or `/data/lancedb`; + point the setting at it, or move it into the checkout. Faiss indexes and + uploads were already stored under the checkout and are unaffected. ## Check your version