about summary refs log tree commit diff
path: root/doc/manual/nix-push.xml
diff options
context:
space:
mode:
authorEelco Dolstra <eelco.dolstra@logicblox.com>2012-11-06T16·45+0100
committerEelco Dolstra <eelco.dolstra@logicblox.com>2012-11-06T16·45+0100
commitbbc107ef1e850d73dbe9a21c567b34f5939570c6 (patch)
treea9ed9bc3394147b44e6bd7b5dc1d3b370b5732b4 /doc/manual/nix-push.xml
parent3a95e1a17cd2755f00c26eb16ffd066bc6aa1a8d (diff)
Process binary caches in order of priority
Binary caches can now specify a priority in their nix-cache-info file.
The binary cache substituter checks caches in order of priority.  This
is to ensure that fast, static caches like nixos.org/binary-cache are
processed before slow, dynamic caches like hydra.nixos.org.
Diffstat (limited to 'doc/manual/nix-push.xml')
-rw-r--r--doc/manual/nix-push.xml11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/manual/nix-push.xml b/doc/manual/nix-push.xml
index 170b6f55ab30..ff0403834269 100644
--- a/doc/manual/nix-push.xml
+++ b/doc/manual/nix-push.xml
@@ -210,6 +210,7 @@ properties.  Here’s an example:
 <screen>
 StoreDir: /nix/store
 WantMassQuery: 1
+Priority: 10
 </screen>
 
 The properties that are currently supported are:
@@ -246,6 +247,16 @@ The properties that are currently supported are:
 
   </varlistentry>
 
+  <varlistentry><term><literal>Priority</literal></term>
+
+    <listitem><para>Each binary cache has a priority (defaulting to
+    50).  Binary caches are checked for binaries in order of ascending
+    priority; thus a higher number denotes a lower priority.  The
+    binary cache <uri>http://nixos.org/binary-cache</uri> has priority
+    40.</para></listitem>
+
+  </varlistentry>
+
 </variablelist>
 
 </para>