forked from Fachschaft/nixConfig
Fixed typo in README.md in curtosy of Gonne see [#13]
This commit is contained in:
parent
3d9fb42fd4
commit
71c5d34cdb
1 changed files with 1 additions and 1 deletions
|
@ -51,7 +51,7 @@ If you keep your application data (like recommended) on a separate partition, th
|
||||||
to interact with this, as most configuration files will be in the nix store anyway. If the application wants these nix
|
to interact with this, as most configuration files will be in the nix store anyway. If the application wants these nix
|
||||||
store files in certain directories you should use `environment.etc` family of options (consult the nixos documentation
|
store files in certain directories you should use `environment.etc` family of options (consult the nixos documentation
|
||||||
for this). This is for mutable files that are not core application data. (Like ssh keys, for a mailserver one could
|
for this). This is for mutable files that are not core application data. (Like ssh keys, for a mailserver one could
|
||||||
think about the hash files (not the db files) of an alias map (if one don't want to manage that with
|
think about the hash files (not the db files) of an alias map (if one doesn't want to manage that with
|
||||||
the nix store), things like that).
|
the nix store), things like that).
|
||||||
|
|
||||||
This should not be (but could be) used for large application databases. It would be more appropriate to mount
|
This should not be (but could be) used for large application databases. It would be more appropriate to mount
|
||||||
|
|
Loading…
Reference in a new issue