commit 5c53b131eb001cd98a2b5862621f6842b9a9cfee
parent ed3e7e62d2968b94c93c30b341911fb1111705aa
Author: Vincent Demeester <vincent@sbr.pm>
Date: Sat, 23 May 2020 12:37:52 +0200
builds: update fedora
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
Diffstat:
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/.builds/fedora.yml b/.builds/fedora.yml
@@ -4,8 +4,11 @@ secrets:
sources:
- git@git.sr.ht:~vdemeester/secrets
tasks:
-- hello: |
- echo "do something with fedora at some point"
+- install_nix: |
+ set -euo pipefail
+ curl -L https://nixos.org/nix/install | sh
+- install_home_manager: |
+ nix-shell $(nix eval --raw '(import ./home/nix/sources.nix).["home-manager"].outPath') -A install
triggers:
- action: email
condition: failure
diff --git a/README.md b/README.md
@@ -91,7 +91,7 @@ soon-ish 👼):
Most of the `make` commands will try to populate this ahead of time. The assumption is :
have a `sync` folder where the assets are. *Note: how to bootstrap (as syncthing will
not be there, and the `sync` folder either)*
-- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#org3f3a0bc).
+- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#org52d6b46).
`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
@@ -101,7 +101,7 @@ soon-ish 👼):
- `private`: holds non-shareable code, like *secrets*.
- `tmp`: things to… organize (e.g. where I import my other *legacy* configuration)
-<a id="org3f3a0bc"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="org52d6b46"></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).