nix-dot-dev/nix.dev
1
1
Fork 0
mirror of https://github.com/nix-dot-dev/nix.dev.git synced 2024-10-06 01:57:36 +03:00
Code Issues Projects Releases Wiki Activity

add additional links and next steps

Browse Source
This commit is contained in:
Valentin Gagarin 2023-02-16 02:36:45 +01:00
parent 91eda534ef
commit a6efa591dc
2 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
source/tutorials/ad-hoc-developer-environments.md
View File

@ -128,15 +128,18 @@ There are two things going on here:
1. The `--pure` flag makes sure that the bash environment from your system is not inherited. That means only the `git` that Nix installed is available inside the shell. This is useful for one-liners and scripts that run, for example, within a CI environment. While developing, however, we'd like to have our editor around and a bunch of other things. Therefore we might skip the flag for development environments but use it in build ones.
2. The `-I` flag pins the Nixpkgs revision to an **exact Git revision**, leaving no doubt about which exact version of Nix packages will be used.
## References
- [Nix manual: `nix-shell`](https://nixos.org/manual/nix/stable/command-ref/nix-shell) or `man nix-shell`
## Next steps
We've only covered the bare essentials of Nix here. Once you're comfortable with these examples, take a look at:
- {ref}`reproducible-scripts` to see how to use `nix-shell` for reproducible scripts.
- {ref}`reading-nix-language` to learn about the Nix language, which is used to declare packages and configurations.
- {ref}`pinning-nixpkgs` to see different ways to import Nixpkgs.
- {ref}`declarative-reproducible-envs` to create reproducible shell environments given a declarative configuration file called a Nix expression.
- [Garbage Collection](https://nixos.org/manual/nix/stable/package-management/garbage-collection.html)- as when using `nix-shell`, packages are downloaded into `/nix/store`, but never removed.
- See `man nix-shell` for all of the options.
- {ref}`declarative-reproducible-envs` to create reproducible shell environments with a declarative configuration file.
- [Garbage Collection](https://nixos.org/manual/nix/stable/package-management/garbage-collection.html) – free up storage used by the programs made available through Nix
- To quickly setup a Nix project read through
[Getting started Nix template](https://github.com/nix-dot-dev/getting-started-nix-template).
- {ref}`reproducible-scripts` to see how to use `nix-shell` as a shebang.

10
source/tutorials/reproducible-scripts.md
View File

@ -35,9 +35,11 @@ It determines which program to use for running the script.
We will use the shebang line `#! /usr/bin/env nix-shell`.
`/usr/bin/env` is a program available on most modern Unix-like operating systems.
[`env`] is a program available on most modern Unix-like operating systems at the file system path `/usr/bin/env`.
It takes a command name as argument and will run the first executable by that name it finds in the directories listed in the environment variable `$PATH`.
[`env`]: https://www.gnu.org/software/coreutils/manual/html_node/env-invocation.html
We use [`nix-shell` as a shebang interpreter].
It takes the following parameters relevant for our use case:
@ -77,3 +79,9 @@ Run the script:
```console
./nixpkgs-releases.sh
```
# Next steps
- {ref}`reading-nix-language` to learn about the Nix language, which is used to declare packages and configurations.
- {ref}`declarative-reproducible-envs` to create reproducible shell environments with a declarative configuration file.
- [Garbage Collection](https://nixos.org/manual/nix/stable/package-management/garbage-collection.html) – free up storage used by the programs made available through Nix