konsti
5386701cc1
Add configuration documentation for the build backend and make it the preview default. The build backend should generally work with default configuration unless you want specific features such as flat layout or module renaming, there is only a dedicated configuration, but no concept or guide page for the build backend. Once the build backend is stable, we can update the guide documentation to explain that uv defaults to its own build backend, but other build backends are also supported. The uv build backend becomes the default in preview, giving it more exposure from users and preparing it to make it the default proper. The current documentation retains warnings that the build backend is in preview. To see current uses of `uv_build` on GitHub: https://github.com/search?q=path%3A**%2Fpyproject.toml+uv_build%3E%3D0&type=code --------- Co-authored-by: Zanie Blue <contact@zanie.dev>
13 lines
423 B
Markdown
13 lines
423 B
Markdown
# Configuration overview
|
|
|
|
Read about the various ways to configure uv:
|
|
|
|
- [Using configuration files](./files.md)
|
|
- [Using environment variables](./environment.md)
|
|
- [Configuring authentication](./authentication.md)
|
|
- [Configuring package indexes](./indexes.md)
|
|
- [The uv build backend](build-backend.md)
|
|
|
|
Or, jump to the [settings reference](../reference/settings.md) which enumerates the available
|
|
configuration options.
|