docs: add Pixi-specific docs about setup, commands and packaging (#23)

Author: DavidVujic

docs/commands.md

@@ -30,6 +30,11 @@ rye run poly create workspace --name my_example_namespace --theme loose
 uv run poly create workspace --name my_example_namespace --theme loose
 ```
 
+#### Pixi
+``` shell
+pixi run poly create workspace --name my_example_namespace --theme loose
+```
+
 #### Maturin
 
 ``` shell
@@ -118,6 +123,11 @@ rye run poly create component --name my_example_component
 uv run poly create component --name my_example_component
 ```
 
+#### Pixi
+``` shell
+pixi run poly create component --name my_example_component
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -160,6 +170,11 @@ rye run poly create base --name my_example_base
 uv run poly create base --name my_example_base
 ```
 
+#### Pixi
+``` shell
+pixi run poly create base --name my_example_base
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -202,6 +217,11 @@ rye run poly create project --name my_example_project
 uv run poly create project --name my_example_project
 ```
 
+#### Pixi
+``` shell
+pixi run poly create project --name my_example_project
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -244,6 +264,11 @@ rye run poly info
 uv run poly info
 ```
 
+#### Pixi
+``` shell
+pixi run poly info
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -292,6 +317,11 @@ rye run poly diff
 uv run poly diff
 ```
 
+#### Pixi
+``` shell
+pixi run poly diff
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -345,6 +375,11 @@ rye run poly libs
 uv run poly libs
 ```
 
+#### Pixi
+``` shell
+pixi run poly libs
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -402,6 +437,11 @@ rye run poly check
 uv run poly check
 ```
 
+#### Pixi
+``` shell
+pixi run poly check
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -456,6 +496,11 @@ rye run poly sync
 uv run poly sync
 ```
 
+#### Pixi
+``` shell
+pixi run poly sync
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -502,6 +547,11 @@ rye run poly deps
 uv run poly deps
 ```
 
+#### Pixi
+``` shell
+pixi run poly deps
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment
@@ -558,6 +608,11 @@ rye run poly test diff
 uv run poly test diff
 ```
 
+#### Pixi
+``` shell
+pixi run poly test diff
+```
+
 #### Maturin
 ``` shell
 # if not already activated a virtual environment

docs/deployment.md

@@ -6,7 +6,7 @@ Packaging and deploying Polylith projects is done by using the Poetry Multiproje
 The `poetry build-project` command will make it possible to use relative package includes as how components and bases are added to Python Polylith projects. 
 Relative includes are currently not possible by default in __Poetry__, that is where the __Multiproject__ plugin comes in.
 
-## Hatch, PDM, Rye and uv
+## Hatch, PDM, Rye, Pixi and uv
 Hatch, PDM, Rye and uv support relative includes via the `[tool.poetry.bricks]` configuration.
 Nothing extra needed other than the build hooks.
 
@@ -16,7 +16,7 @@ you will need to add the path in the project-specific `pyroject.toml`.
 
 If you only provide `wheel` distributions, this is optional.
 
-#### Hatch, Rye and uv
+#### Hatch, Rye, Pixi and uv
 ```toml
 [tool.hatch.build.targets.wheel]
 packages = ["<your top namespace here>"]
@@ -77,6 +77,17 @@ _Are you using the `uv` build backend (and not the recommended `hatch` build bac
 _If so, you need to run the `poly build setup` and `poly build teardown` commands before and after the `uv build` command._
 _This is needed because of the missing build hook support of the uv build backend._
 
+#### Pixi
+``` shell
+cd projects/the_project
+
+pixi run poly build setup
+
+pixi build
+
+pixi run poly build teardown
+```
+
 #### Maturin
 ``` shell
 cd projects/the_project

docs/setup.md

@@ -265,8 +265,9 @@ __Choose the name wisely.__ Have a look in [PEP-423](https://peps.python.org/pep
 `--theme` the structure of the workspace, `loose` is the recommended structure for Python.
 
 ### Pixi
-Have a look at the Hatch and Maturin sections for setup, packaging and usage. More details about Pixi setup coming soon!
-As of this writing, Pixi has experimental support for building and packaging. The Hatch-specific hooks is not (currently) needed for Pixi.
+Have a look at the Pixi docs for initializing a new repo or project.
+For the Polylith initial setup, look at the __Hatch__ sections at this page.
+
 
 ### Pantsbuild (aka Pants)
 Have a look in the Pants-specific [example repository](examples.md) for details on the setup.