Undocument NIX_OTHER_STORES
This commit is contained in:
parent
57f6463ec0
commit
b1af336132
3 changed files with 2 additions and 49 deletions
|
@ -283,28 +283,6 @@ $ mount -o bind /mnt/otherdisk/nix /nix</screen>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
|
||||||
<varlistentry xml:id="envar-other-stores"><term><envar>NIX_OTHER_STORES</envar></term>
|
|
||||||
|
|
||||||
<listitem><para>This variable contains the paths of remote Nix
|
|
||||||
installations from which packages can be copied, separated by colons.
|
|
||||||
<phrase condition="manual">See <xref linkend="sec-sharing-packages"
|
|
||||||
/> for details.</phrase> Each path should be the
|
|
||||||
<filename>/nix</filename> directory of a remote Nix installation
|
|
||||||
(i.e., not the <filename>/nix/store</filename> directory). The
|
|
||||||
paths are subject to globbing, so you can set it so something like
|
|
||||||
<literal>/var/run/nix/remote-stores/*/nix</literal> and mount
|
|
||||||
multiple remote filesystems in
|
|
||||||
<literal>/var/run/nix/remote-stores</literal>.</para>
|
|
||||||
|
|
||||||
<para>Note that if you’re building through the <link
|
|
||||||
linkend="sec-nix-daemon">Nix daemon</link>, the only setting for
|
|
||||||
this variable that matters is the one that the
|
|
||||||
<command>nix-daemon</command> process uses. So if you want to
|
|
||||||
change it, you have to restart the daemon.</para></listitem>
|
|
||||||
|
|
||||||
</varlistentry>
|
|
||||||
|
|
||||||
|
|
||||||
<varlistentry><term><envar>NIX_SHOW_STATS</envar></term>
|
<varlistentry><term><envar>NIX_SHOW_STATS</envar></term>
|
||||||
|
|
||||||
<listitem><para>If set to <literal>1</literal>, Nix will print some
|
<listitem><para>If set to <literal>1</literal>, Nix will print some
|
||||||
|
|
|
@ -25,7 +25,7 @@
|
||||||
<holder>Eelco Dolstra</holder>
|
<holder>Eelco Dolstra</holder>
|
||||||
</copyright>
|
</copyright>
|
||||||
|
|
||||||
<date>April 2014</date>
|
<date>September 2014</date>
|
||||||
|
|
||||||
</info>
|
</info>
|
||||||
|
|
||||||
|
|
|
@ -53,30 +53,5 @@ But note that <command>nix-copy-closure</command> is generally more
|
||||||
efficient in this example because it only copies paths that are not
|
efficient in this example because it only copies paths that are not
|
||||||
already present in the target Nix store.</para>
|
already present in the target Nix store.</para>
|
||||||
|
|
||||||
<para>Finally, if you can mount the Nix store of a remote machine in
|
|
||||||
your local filesystem, Nix can copy paths from the remote Nix store to
|
|
||||||
the local Nix store <emphasis>on demand</emphasis>. For instance,
|
|
||||||
suppose that you mount a remote machine containing a Nix store via
|
|
||||||
<command
|
|
||||||
xlink:href="http://fuse.sourceforge.net/sshfs.html">sshfs</command>:
|
|
||||||
|
|
||||||
<screen>
|
</chapter>
|
||||||
$ sshfs alice@itchy.example.org:/ /mnt</screen>
|
|
||||||
|
|
||||||
You should then set the <envar>NIX_OTHER_STORES</envar> environment
|
|
||||||
variable to tell Nix about this remote Nix store:
|
|
||||||
|
|
||||||
<screen>
|
|
||||||
$ export NIX_OTHER_STORES=/mnt/nix</screen>
|
|
||||||
|
|
||||||
Then if you do any Nix operation, e.g.
|
|
||||||
|
|
||||||
<screen>
|
|
||||||
$ nix-env -i firefox</screen>
|
|
||||||
|
|
||||||
and Nix has to build a path that it sees is already present in
|
|
||||||
<filename>/mnt/nix</filename>, then it will just copy from there
|
|
||||||
instead of building it from source.</para>
|
|
||||||
|
|
||||||
|
|
||||||
</chapter>
|
|
||||||
|
|
Loading…
Reference in a new issue