commit 93fa09baf3f1882c5412e52ce6c3b143b5575a13
parent cf9e0f43a7de2291b9484df4b1213b60c49fad46
Author: Vincent Demeester <vincent@sbr.pm>
Date: Wed, 8 Jul 2020 18:21:09 +0200
direnv: disable use_nix for now
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
Diffstat:
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/.envrc b/.envrc
@@ -1,2 +1,3 @@
-use_nix shell.nix
+# use_nix shell.nix
test -f .secrets && source .secrets || echo "no secrets"
+export QEMU_OPTS="-m 8096 -cpu host"
diff --git a/README.md b/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](#orgfbae953).
+- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#orgbc889c3).
`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="orgfbae953"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="orgbc889c3"></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).
