-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fully document pixi.toml format #308
Comments
Yes you are completely right. A detailed document about the details of the |
And here it is: https://prefix.dev/docs/pixi/configuration |
Awesome, I see there are a lot of proposed enhancements to pixi.toml (as well as supporting pyproject.toml). It would be great to ensure that any such changes are also documented as soon as they land! Thanks! Pixi is looking really great! I also notice that you reference |
Yeah we should definitely pay attention to update the docs as we add/change features. We will be merging the docs in this repository soon so we can make sure they are updated with a PR.
|
I think it'd be fine to keep reference to it, but make note that it's coming soon (and if you have time add a page about pixi build with a huge header that says it's not available yet and links to the issue). |
I updated it in the new documentation! |
Problem description
Hi, I think to increase the ease of adopting pixi, please document fully all the different options in the pixi.toml format and explain each section.
Most of the basics are available, but when I look at examples, there are some uses like (build-dependencies) and host/target that aren't fully documented.
Also some references to other package managers and their features and how they can be replicated within pixi would be helpful (for example dependency groups or optional dependencies).
The text was updated successfully, but these errors were encountered: