Deployed 7dbdddf to dev with MkDocs 1.6.1 and mike 2.0.0

Author: github-actions[bot]

dev/Community/index.html

@@ -2164,7 +2164,7 @@
 
 
 <h1 id="community">Community<a class="headerlink" href="#community" title="Permanent link">#</a></h1>
-<p>When you want to show your users and contributors that they can use pixi in your repo, you can use the following badge:</p>
+<p>When you want to show your users and contributors that they can use Pixi in your repo, you can use the following badge:</p>
 <p><a href="https://pixi.sh"><img alt="Pixi Badge" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/prefix-dev/pixi/main/assets/badge/v0.json" /></a></p>
 <div class="language-text highlight"><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a>[![Pixi Badge](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/prefix-dev/pixi/main/assets/badge/v0.json)](https://pixi.sh)
 </span></code></pre></div>
@@ -2217,7 +2217,7 @@ <h2 id="built-using-pixi">Built using Pixi<a class="headerlink" href="#built-usi
 </ul>
 <ul>
 <li><a href="https://github.com/pavelzw/pixi-pycharm">pixi-pycharm</a>: Conda shim for PyCharm that proxies pixi</li>
-<li><a href="https://github.com/pavelzw/pixi-diff-to-markdown">pixi-diff-to-markdown</a>: Generate markdown summaries from pixi update</li>
+<li><a href="https://github.com/pavelzw/pixi-diff-to-markdown">pixi-diff-to-markdown</a>: Generate markdown summaries from Pixi update</li>
 <li><a href="https://github.com/jiaxiyang/cpp_project_guideline">jiaxiyang/cpp_project_guideline</a>: Guide the way beginners make their c++ projects.</li>
 <li><a href="https://github.com/hex-inc/vegafusion">hex-inc/vegafusion</a>: Serverside scaling of Vega and Altair visualizations in Rust, Python, WASM, and Java</li>
 <li><a href="https://github.com/pablovela5620/arxiv-researcher">pablovela5620/arxiv-researcher</a>: Summarize PDF's and Arixv papers with Langchain and Nougat 🦉</li>

dev/FAQ/index.html

@@ -2274,7 +2274,7 @@ <h2 id="why-the-name-pixi">Why the name <code>pixi</code><a class="headerlink" h
 </div>
 <h2 id="where-is-pixi-build">Where is <code>pixi build</code><a class="headerlink" href="#where-is-pixi-build" title="Permanent link">#</a></h2>
 <p><strong>TL;DR</strong>: It's coming we promise!</p>
-<p><code>pixi build</code> is going to be the subcommand that can generate a conda package out of a pixi project.
+<p><code>pixi build</code> is going to be the subcommand that can generate a conda package out of a Pixi project.
 This requires a solid build tool which we're creating with <a href="https://github.com/prefix-dev/rattler-build"><code>rattler-build</code></a> which will be used as a library in pixi.</p>
 
 

dev/__pycache__/docs_hooks.cpython-312.pyc

@@ -2477,18 +2477,18 @@ <h1>Info Command</h1>
 </span><span id="__span-0-26"><a id="__codelineno-0-26" name="__codelineno-0-26" href="#__codelineno-0-26"></a>             Tasks: docs, test-all, test, build, lint, install, build-docs
 </span></code></pre></div>
 <h2 id="global-info">Global info<a class="headerlink" href="#global-info" title="Permanent link">#</a></h2>
-<p>The first part of the info output is information that is always available and tells you what pixi can read on your machine.</p>
+<p>The first part of the info output is information that is always available and tells you what Pixi can read on your machine.</p>
 <h3 id="platform">Platform<a class="headerlink" href="#platform" title="Permanent link">#</a></h3>
 <p>This defines the platform you're currently on according to pixi.
-If this is incorrect, please file an issue on the <a href="https://github.com/prefix-dev/pixi">pixi repo</a>.</p>
+If this is incorrect, please file an issue on the <a href="https://github.com/prefix-dev/pixi">Pixi repo</a>.</p>
 <h3 id="virtual-packages">Virtual packages<a class="headerlink" href="#virtual-packages" title="Permanent link">#</a></h3>
-<p>The virtual packages that pixi can find on your machine.</p>
+<p>The virtual packages that Pixi can find on your machine.</p>
 <p>In the Conda ecosystem, you can depend on virtual packages.
 These packages aren't real dependencies that are going to be installed, but rather are being used in the solve step to find if a package can be installed on the machine.
 A simple example: When a package depends on Cuda drivers being present on the host machine it can do that by depending on the <code>__cuda</code> virtual package.
-In that case, if pixi cannot find the <code>__cuda</code> virtual package on your machine the installation will fail.</p>
+In that case, if Pixi cannot find the <code>__cuda</code> virtual package on your machine the installation will fail.</p>
 <h3 id="cache-dir">Cache dir<a class="headerlink" href="#cache-dir" title="Permanent link">#</a></h3>
-<p>The directory where pixi stores its cache.
+<p>The directory where Pixi stores its cache.
 Checkout the <a href="../../environments/environment/#caching-packages">cache documentation</a> for more information.</p>
 <h3 id="auth-storage">Auth storage<a class="headerlink" href="#auth-storage" title="Permanent link">#</a></h3>
 <p>Check the <a href="../../deployment/authentication/">authentication documentation</a></p>
@@ -2501,7 +2501,7 @@ <h2 id="workspace-info">Workspace info<a class="headerlink" href="#workspace-inf
 <h3 id="manifest-file">Manifest file<a class="headerlink" href="#manifest-file" title="Permanent link">#</a></h3>
 <p>The path to the <a href="../../reference/pixi_manifest/">manifest file</a> that describes the workspace.</p>
 <h3 id="last-updated">Last updated<a class="headerlink" href="#last-updated" title="Permanent link">#</a></h3>
-<p>The last time the lock file was updated, either manually or by pixi itself.</p>
+<p>The last time the lock file was updated, either manually or by Pixi itself.</p>
 <h2 id="environment-info">Environment info<a class="headerlink" href="#environment-info" title="Permanent link">#</a></h2>
 <p>The environment info defined per environment. If you don't have any environments defined, this will only show the <code>default</code> environment.</p>
 <h3 id="features">Features<a class="headerlink" href="#features" title="Permanent link">#</a></h3>

dev/advanced/explain_info_command/index.html

@@ -2448,7 +2448,7 @@ <h2 id="update">Update<a class="headerlink" href="#update" title="Permanent link
 <p>Updating is as simple as installing, rerunning the installation script gets you the latest version.</p>
 <p><div class="language-shell highlight"><pre><span></span><code><span id="__span-2-1"><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a>pixi<span class="w"> </span>self-update
 </span></code></pre></div>
-Or get a specific pixi version using:
+Or get a specific Pixi version using:
 <div class="language-shell highlight"><pre><span></span><code><span id="__span-3-1"><a id="__codelineno-3-1" name="__codelineno-3-1" href="#__codelineno-3-1"></a>pixi<span class="w"> </span>self-update<span class="w"> </span>--version<span class="w"> </span>x.y.z
 </span></code></pre></div></p>
 <div class="admonition note">
@@ -2457,20 +2457,20 @@ <h2 id="update">Update<a class="headerlink" href="#update" title="Permanent link
 you must use the built-in update mechanism. e.g. <code>brew upgrade pixi</code>.</p>
 </div>
 <h2 id="alternative-installation-methods">Alternative Installation Methods<a class="headerlink" href="#alternative-installation-methods" title="Permanent link">#</a></h2>
-<p>Although we recommend installing pixi through the above method we also provide additional installation methods.</p>
+<p>Although we recommend installing Pixi through the above method we also provide additional installation methods.</p>
 <h3 id="homebrew">Homebrew<a class="headerlink" href="#homebrew" title="Permanent link">#</a></h3>
-<p>Pixi is available via homebrew. To install pixi via homebrew simply run:</p>
+<p>Pixi is available via homebrew. To install Pixi via homebrew simply run:</p>
 <div class="language-shell highlight"><pre><span></span><code><span id="__span-4-1"><a id="__codelineno-4-1" name="__codelineno-4-1" href="#__codelineno-4-1"></a>brew<span class="w"> </span>install<span class="w"> </span>pixi
 </span></code></pre></div>
 <h3 id="windows-installer">Windows Installer<a class="headerlink" href="#windows-installer" title="Permanent link">#</a></h3>
 <p>We provide an <code>msi</code> installer on <a href="https://github.com/prefix-dev/pixi/releases/latest">our GitHub releases page</a>.
-The installer will download pixi and add it to the path.</p>
+The installer will download Pixi and add it to the path.</p>
 <h3 id="winget">Winget<a class="headerlink" href="#winget" title="Permanent link">#</a></h3>
 <div class="language-text highlight"><pre><span></span><code><span id="__span-5-1"><a id="__codelineno-5-1" name="__codelineno-5-1" href="#__codelineno-5-1"></a>winget install prefix-dev.pixi
 </span></code></pre></div>
 <h3 id="install-from-source">Install From Source<a class="headerlink" href="#install-from-source" title="Permanent link">#</a></h3>
 <p>pixi is 100% written in Rust, and therefore it can be installed, built and tested with cargo.
-To start using pixi from a source build run:</p>
+To start using Pixi from a source build run:</p>
 <div class="language-shell highlight"><pre><span></span><code><span id="__span-6-1"><a id="__codelineno-6-1" name="__codelineno-6-1" href="#__codelineno-6-1"></a>cargo<span class="w"> </span>install<span class="w"> </span>--locked<span class="w"> </span>--git<span class="w"> </span>https://github.com/prefix-dev/pixi.git<span class="w"> </span>pixi
 </span></code></pre></div>
 <p>We don't publish to <code>crates.io</code> anymore, so you need to install it from the repository.
@@ -2497,7 +2497,7 @@ <h2 id="installer-script-options">Installer Script Options<a class="headerlink"
 <tbody>
 <tr>
 <td><code>PIXI_VERSION</code></td>
-<td>The version of pixi getting installed, can be used to up- or down-grade.</td>
+<td>The version of Pixi getting installed, can be used to up- or down-grade.</td>
 <td><code>latest</code></td>
 </tr>
 <tr>
@@ -2507,7 +2507,7 @@ <h2 id="installer-script-options">Installer Script Options<a class="headerlink"
 </tr>
 <tr>
 <td><code>PIXI_ARCH</code></td>
-<td>The architecture the pixi version was built for.</td>
+<td>The architecture the Pixi version was built for.</td>
 <td><code>uname -m</code></td>
 </tr>
 <tr>
@@ -2544,7 +2544,7 @@ <h2 id="installer-script-options">Installer Script Options<a class="headerlink"
 <tr>
 <td><code>PixiVersion</code></td>
 <td><code>PIXI_VERSION</code></td>
-<td>The version of pixi getting installed, can be used to up- or down-grade.</td>
+<td>The version of Pixi getting installed, can be used to up- or down-grade.</td>
 <td><code>latest</code></td>
 </tr>
 <tr>

dev/advanced/installation/index.html

@@ -2134,7 +2134,7 @@ <h1 id="using-pixi-exec-to-create-self-contained-scripts">Using <code>pixi exec<
 So in total, <code>pixi exec --spec bat -- bash -e use-bat.sh</code> is being executed when you run <code>./use-bat.sh</code>.</p>
 </div>
 <p>You can also write self-contained python files that ship with their dependencies.
-This example shows a very simple CLI that installs a pixi environment to an arbitrary prefix using <a href="https://conda.github.io/rattler/py-rattler"><code>py-rattler</code></a> and <a href="https://typer.tiangolo.com"><code>typer</code></a>.</p>
+This example shows a very simple CLI that installs a Pixi environment to an arbitrary prefix using <a href="https://conda.github.io/rattler/py-rattler"><code>py-rattler</code></a> and <a href="https://typer.tiangolo.com"><code>typer</code></a>.</p>
 <div class="language-python highlight"><span class="filename">install-pixi-environment-to-prefix.py</span><pre><span></span><code><span id="__span-1-1"><a id="__codelineno-1-1" name="__codelineno-1-1" href="#__codelineno-1-1"></a><span class="ch">#!/usr/bin/env -S pixi exec --spec py-rattler&gt;=0.10.0,&lt;0.11 --spec typer&gt;=0.15.0,&lt;0.16 -- python</span>
 </span><span id="__span-1-2"><a id="__codelineno-1-2" name="__codelineno-1-2" href="#__codelineno-1-2"></a>
 </span><span id="__span-1-3"><a id="__codelineno-1-3" name="__codelineno-1-3" href="#__codelineno-1-3"></a><span class="kn">import</span><span class="w"> </span><span class="nn">asyncio</span>

dev/advanced/shebang/index.html

@@ -2177,9 +2177,9 @@
 
   <h1>Build Backends</h1>
 
-<p>To decouple the building of a conda package from pixi we provide something what are called build backends.
-These are essentially executables following a specific protocol that is implemented for both pixi and the build backend.
-This also allows for decoupling of the build backend from pixi and it's manifest specification.</p>
+<p>To decouple the building of a conda package from Pixi we provide something what are called build backends.
+These are essentially executables following a specific protocol that is implemented for both Pixi and the build backend.
+This also allows for decoupling of the build backend from Pixi and it's manifest specification.</p>
 <p>The backends we are currently developing are available in the following <a href="https://prefix.dev/channels/pixi-build-backends">conda channel</a>.
 And are being developed in the <a href="https://github.com/prefix-dev/pixi-build-backends">pixi-build-backends</a> repository.</p>
 <h3 id="installation">Installation<a class="headerlink" href="#installation" title="Permanent link">#</a></h3>
@@ -2192,7 +2192,7 @@ <h3 id="installation">Installation<a class="headerlink" href="#installation" tit
 </span><span id="__span-0-6"><a id="__codelineno-0-6" name="__codelineno-0-6" href="#__codelineno-0-6"></a><span class="p">]</span>
 </span></code></pre></div>
 <ol>
-<li>This will allow pixi to install desired backends from the <code>pixi-build-backends</code> channel, and any requirements from <code>conda-forge</code>. Backends are installed into isolated environments, and will be shared across pixi workspaces.</li>
+<li>This will allow Pixi to install desired backends from the <code>pixi-build-backends</code> channel, and any requirements from <code>conda-forge</code>. Backends are installed into isolated environments, and will be shared across Pixi workspaces.</li>
 </ol>
 <h3 id="overriding-the-build-backend">Overriding the Build Backend<a class="headerlink" href="#overriding-the-build-backend" title="Permanent link">#</a></h3>
 <p>Sometimes you want to override the build backend that is used by pixi. Meaning overriding the backend that is specified in the <a href="../../reference/pixi_manifest/#the-build-system"><code>[package.build]</code></a>. We currently have two environment variables that allow for this:</p>

dev/build/backends/index.html

@@ -2287,7 +2287,7 @@
 
 <h1 id="tutorial-building-a-c-package">Tutorial: Building a C++ package<a class="headerlink" href="#tutorial-building-a-c-package" title="Permanent link">#</a></h1>
 <p>This example shows how to build a C++ package with CMake and use it together with <code>pixi-build</code>.
-To read more about how building packages work with pixi see the <a href="../getting_started/">Getting Started</a> guide.</p>
+To read more about how building packages work with Pixi see the <a href="../getting_started/">Getting Started</a> guide.</p>
 <p>We'll start off by creating a workspace that use <a href="https://github.com/wjakob/nanobind">nanobind</a> to build Python bindings.
 That we can also test using pixi.
 We'll later combine this example together with a Python package.</p>
@@ -2348,7 +2348,7 @@ <h3 id="the-pixitoml-file">The <code>pixi.toml</code> file<a class="headerlink"
 </span><span id="__span-2-28"><a id="__codelineno-2-28" name="__codelineno-2-28" href="#__codelineno-2-28"></a><span class="n">python</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s2">&quot;3.12.*&quot;</span><span class="w">  </span><span class="c1"># (7)!</span>
 </span></code></pre></div>
 <ol>
-<li>Add the <strong>preview</strong> feature <code>pixi-build</code> that enables pixi to build the package.</li>
+<li>Add the <strong>preview</strong> feature <code>pixi-build</code> that enables Pixi to build the package.</li>
 <li>These are the workspace dependencies. We add our own package as well as Python so that we can later run our package.</li>
 <li>Let's add a task that will run our test</li>
 <li>This is where we specify the package name and version.
@@ -2419,9 +2419,9 @@ <h2 id="testing-if-everything-works">Testing if everything works<a class="header
 </span></code></pre></div>
 <p>This command builds the bindings, installs them and then runs the <code>test</code> task.</p>
 <h2 id="conclusion">Conclusion<a class="headerlink" href="#conclusion" title="Permanent link">#</a></h2>
-<p>In this tutorial, we created a pixi package using C++.
+<p>In this tutorial, we created a Pixi package using C++.
 It can be used as-is, to upload to a conda channel.
-In another tutorial we will learn how to add multiple pixi packages to the same workspace and let one pixi package use another.</p>
+In another tutorial we will learn how to add multiple Pixi packages to the same workspace and let one Pixi package use another.</p>
 <p>Thanks for reading! Happy Coding 🚀</p>
 <p>Any questions? Feel free to reach out or share this tutorial on <a href="https://twitter.com/prefix_dev">X</a>, <a href="https://discord.gg/kKV8ZxyzY4">join our Discord</a>, <a href="mailto:hi@prefix.dev">e-mail</a> us or follow our <a href="https://github.com/prefix-dev">GitHub</a>.</p>
 

dev/build/cpp/index.html

@@ -2196,7 +2196,7 @@
   <h1>Getting started</h1>
 
 <h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">#</a></h2>
-<p>Next to managing workflows and environments, pixi can also build packages.
+<p>Next to managing workflows and environments, Pixi can also build packages.
 This is useful for the following reasons:</p>
 <ul>
 <li>Building and uploading a package to a conda channel</li>
@@ -2216,7 +2216,7 @@ <h2 id="introduction">Introduction<a class="headerlink" href="#introduction" tit
 </ol>
 </div>
 <h2 id="setting-up-the-manifest">Setting up the Manifest<a class="headerlink" href="#setting-up-the-manifest" title="Permanent link">#</a></h2>
-<p>This is an overview of the pixi manifest using <code>pixi-build</code>.</p>
+<p>This is an overview of the Pixi manifest using <code>pixi-build</code>.</p>
 <div class="language-toml highlight"><span class="filename">pixi.toml</span><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a><span class="c1"># Specifies properties for the whole workspace</span>
 </span><span id="__span-0-2"><a id="__codelineno-0-2" name="__codelineno-0-2" href="#__codelineno-0-2"></a><span class="k">[workspace]</span>
 </span><span id="__span-0-3"><a id="__codelineno-0-3" name="__codelineno-0-3" href="#__codelineno-0-3"></a><span class="n">preview</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="p">[</span><span class="s2">&quot;pixi-build&quot;</span><span class="p">]</span>