NixOS/nix.dev
NixOS/nix.dev
1
0
Fork 0
mirror of https://github.com/NixOS/nix.dev.git synced 2024-10-18 14:32:43 -04:00
Code Activity
nix.dev/source/reference/nix-manual.md

43 lines
1.3 KiB
Markdown
Raw Normal View History

host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
(nix-manual)=
# Nix reference manual
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
<!--
This page is pre-processed before rendering with Sphinx. For details:
grep -n nix-manual.md default.nix
-->
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
```{toctree}
:hidden:
Nix pre-release (development) <https://hydra.nixos.org/job/nix/master/build.x86_64-linux/latest/download>
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
Nix @latest@ (latest) <https://nix.dev/manual/nix/latest/>
Nix @rolling@ (in rolling) <https://nix.dev/manual/nix/rolling/>
Nix @stable@ (in stable @nixpkgs-stable@) <https://nix.dev/manual/nix/stable/>
Nix @prev-stable@ (in stable @nixpkgs-prev-stable@) <https://nix.dev/manual/nix/prev-stable/>
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
```
- [Nix pre-release](https://hydra.nixos.org/job/nix/master/build.x86_64-linux/latest/download)
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
Latest build from the `master` branch of the [Nix repository](https://github.com/NixOS/nix)
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
- [Nix @latest@](https://nix.dev/manual/nix/latest/)
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
Latest Nix release
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
- [Nix @rolling@](https://nix.dev/manual/nix/rolling/)
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
Shipped with the {term}`Nixpkgs` and {term}`NixOS` rolling release
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
- [Nix @stable@](https://nix.dev/manual/nix/stable/)
host Nix reference manual on nix.dev this is the most cursed setup you will see any time soon. we're dumping the Nix manual unchanged into the build tree *after* building. the reason is that we'd want to link to it from our table of contents, but because Sphinx does not allow adding arbitrary files to the build output in arbitrary locations (only `_static` works). but we want to place the manual behind a particular URL, and the alternative of maintaining URL rewrites (e.g. in nginx) is not accessible here because the infrastructure is managed somewhere else. now that the files won't appear in their desired locations at Sphinx build time, we can't use relative links to reference them, therefore we have to resort to pointing to the web URL the manual will appear at. this is terrible and I'm sorry. please fix this if you have a better idea. once we use URLs though, we have to avoid linkchecking, since those files may not be there before deploying them. figuring all of this out took way longer than anyone would wish. Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
2023-10-18 06:04:34 -04:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
Shipped with the current {term}`Nixpkgs` and {term}`NixOS` @nixpkgs-stable@ stable release
link to new Nix reference manual page
2023-11-26 18:13:51 -05:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
- [Nix @prev-stable@](https://nix.dev/manual/nix/prev-stable/)
NixOS 23.11 was released
2023-12-04 10:52:49 -05:00
generate index page from structured data - refactor `default.nix` for hopefully better readability - de-noise the overview page text
2023-12-05 21:31:01 -05:00
Shipped with the previous {term}`Nixpkgs` and {term}`NixOS` @nixpkgs-prev-stable@ stable release
NixOS 23.11 was released
2023-12-04 10:52:49 -05:00
link to new Nix reference manual page
2023-11-26 18:13:51 -05:00
:::{tip}
More information on Nixpkgs and NixOS releases: [](channel-branches)
:::
Copy permalink