Commit 3e2a23a628ec

Vincent Demeester <vincent@sbr.pm>
2020-07-16 17:10:59
builds: use nix-build for pkgs for cachix
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
main
1 parent d88ebe5
Changed files (2)
.builds
nix-pkgs.yml
README.md
.builds/nix-pkgs.yml
@@ -11,7 +11,7 @@ tasks:
     set +x
     export CACHIX_SIGNING_KEY=$(cat ~/.cachix.key)
     set -x
-    nix build --verbose -f home/ci.nix cacheOutputs | cachix push shortbrain
+    nix-build --no-out-link home/ci.nix -A cacheOutputs | cachix push shortbrain
 - nur-update: |
     curl -XPOST "https://nur-update.herokuapp.com/update?repo=vdemeester"
 triggers:
README.md
@@ -47,7 +47,7 @@ dramatically or even not working anymore 😛.
 This is probably gonna be a moving target, but this is how it looks (or should look
 soon-ish 👼):
 
--   `docs`: holds documentation about this code, literate configuration, see [literate configuration](#orgbc889c3).
+-   `docs`: holds documentation about this code, literate configuration, see [literate configuration](#orgdb1ed6a).
     `make publish` will publish the `README.org` and the `docs` folder to my website.
 -   `lib`: shared code used during configuration (mostly `nix` code).
 -   `machines`: configuration per machines
@@ -59,7 +59,7 @@ soon-ish 👼):
     will contain empty secrets (or random ones).
 -   `tmp`: things to… organize (e.g. where I import my other *legacy* configuration)
 
-<a id="orgbc889c3"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="orgdb1ed6a"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
 literate configuration files in this repository, I have to think of how to organize files
 in order to end up with one huge file. The goal of having those `org-mode` files, is
 mainly to document my configuration and publish it, most likely on [sbr.pm](https://sbr.pm).