docs(src/assets/): update pixi official documentation

Author: KemingHe

src/assets/pixi/_metadata.json

@@ -1,6 +1,6 @@
 {
   "source_repo": "prefix-dev/pixi",
   "docs_path": "docs",
-  "updated_at": "2025-08-19T22:05:16Z",
-  "commit_sha": "167b115daa9ba771f96e27008ea0fe6313bab0ad"
+  "updated_at": "2025-08-26T22:05:24Z",
+  "commit_sha": "77a0a4c9a6d76d7389a48c3c2aa91ae1ed2c2a13"
 }

src/assets/pixi/global_tools/introduction.md

@@ -57,6 +57,79 @@ You can run `py3` to start the python interpreter.
 py3 -c "print('Hello World')"
 ```
 
+## Install Dependencies From Source
+
+Pixi global also allows you to install [Pixi packages](../build/getting_started.md).
+Let's assume there's a C++ package we'd like to install globally from source.
+First, it needs to have a package manifest:
+
+```toml title="pixi.toml"
+[package] 
+name = "cpp_math"
+version = "0.1.0"
+
+[package.build]
+backend = { name = "pixi-build-cmake", version = "*" }
+```
+
+If the source is on your machine, you can install it like this:
+
+```shell
+pixi global install --path /path/to/cpp_math
+```
+
+If the source resides in a git repository, you can access it like this:
+
+```shell
+pixi global install --git https://github.com/ORG_NAME/cpp_math.git
+```
+
+One has to take care if the source contains multiple outputs, see for example this recipe:
+
+```yaml title="recipe.yaml"
+recipe:
+  name: multi-output
+  version: "0.1.0"
+
+outputs:
+  - package:
+      name: foobar
+    build:
+      script:
+        - if: win
+          then:
+            - mkdir -p %PREFIX%\bin
+            - echo @echo off > %PREFIX%\bin\foobar.bat
+            - echo echo Hello from foobar >> %PREFIX%\bin\foobar.bat
+          else:
+            - mkdir -p $PREFIX/bin
+            - echo "#!/usr/bin/env bash" > $PREFIX/bin/foobar
+            - echo "echo Hello from foobar" >> $PREFIX/bin/foobar
+            - chmod +x $PREFIX/bin/foobar
+
+  - package:
+      name: bizbar
+    build:
+      script:
+        - if: win
+          then:
+            - mkdir -p %PREFIX%\bin
+            - echo @echo off > %PREFIX%\bin\bizbar.bat
+            - echo echo Hello from bizbar >> %PREFIX%\bin\bizbar.bat
+          else:
+            - mkdir -p $PREFIX/bin
+            - echo "#!/usr/bin/env bash" > $PREFIX/bin/bizbar
+            - echo "echo Hello from bizbar" >> $PREFIX/bin/bizbar
+            - chmod +x $PREFIX/bin/bizbar
+```
+
+In this case, we have to specify which output we want to install:
+
+```shell
+pixi global install --path /path/to/package foobar
+```
+
+
 ## Shell Completions
 
 When you work in a terminal, you are using a shell and shells can process completions of command line tools.

src/assets/pixi/reference/cli/pixi/global.md

@@ -24,6 +24,7 @@ pixi global <COMMAND>
 | [`expose`](global/expose.md) | Interact with the exposure of binaries in the global environment |
 | [`shortcut`](global/shortcut.md) | Interact with the shortcuts on your machine |
 | [`update`](global/update.md) | Updates environments in the global environment |
+| [`tree`](global/tree.md) | Show a tree of dependencies for a specific global environment |
 
 
 ## Description

src/assets/pixi/reference/cli/pixi/global/tree.md

@@ -0,0 +1,31 @@
+<!--- This file is autogenerated. Do not edit manually! -->
+# <code>[pixi](../../pixi.md) [global](../global.md) tree</code>
+
+## About
+Show a tree of dependencies for a specific global environment
+
+--8<-- "docs/reference/cli/pixi/global/tree_extender:description"
+
+## Usage
+```
+pixi global tree [OPTIONS] --environment <ENVIRONMENT> [REGEX]
+```
+
+## Arguments
+- <a id="arg-<REGEX>" href="#arg-<REGEX>">`<REGEX>`</a>
+:  List only packages matching a regular expression
+
+## Options
+- <a id="arg---environment" href="#arg---environment">`--environment (-e) <ENVIRONMENT>`</a>
+:  The environment to list packages for
+<br>**required**: `true`
+- <a id="arg---invert" href="#arg---invert">`--invert (-i)`</a>
+:  Invert tree and show what depends on a given package in the regex argument
+
+## Description
+Show a tree of a global environment dependencies
+
+Dependency names highlighted in green are directly specified in the manifest.
+
+
+--8<-- "docs/reference/cli/pixi/global/tree_extender:example"

src/assets/pixi/workspace/lockfile.md

@@ -103,7 +103,7 @@ Running the following commands will check and automatically update the lock file
 All the commands that support the interaction with the lock file also include some lock file usage options:
 
 - `--frozen`: install the environment as defined in the lock file, doesn't update `pixi.lock` if it isn't up-to-date with [manifest file](../reference/pixi_manifest.md). It can also be controlled by the `PIXI_FROZEN` environment variable (example: `PIXI_FROZEN=true`).
-- `--locked`: only install if the `pixi.lock` is up-to-date with the [manifest file](../reference/pixi_manifest.md)[^1]. It can also be controlled by the `PIXI_LOCKED` environment variable (example: `PIXI_LOCKED=true`). Conflicts with `--frozen`.
+- `--locked`: only install if the `pixi.lock` is up-to-date with the [manifest file](../reference/pixi_manifest.md). It can also be controlled by the `PIXI_LOCKED` environment variable (example: `PIXI_LOCKED=true`). Conflicts with `--frozen`.
 
 !!! Note "Syncing the lock file with the manifest file"
     The lock file is always matched with the whole configuration in the manifest file.