home

commit 1f00c91b4704c5de0bf64646adaae03813aa23db
parent a5cd6c779bd900f0c0280b18f58d2ef73f040291
Author: Vincent Demeester <vincent@sbr.pm>
Date:   Sat,  6 Jun 2020 17:08:12 +0200

Remove config.nix (not used anymore)

Signed-off-by: Vincent Demeester <vincent@sbr.pm>

Diffstat:
M
README.md
 | 
7
++++---
D
config.nix
 | 
8
--------

2 files changed, 4 insertions(+), 11 deletions(-)
diff --git a/README.md b/README.md
@@ -9,6 +9,7 @@
 4.  [References](#h:e5a95a68-f031-438b-831c-824803d0bc3e)
 5.  [COPYING](#h:716e598e-3b1a-4e48-a72b-608c3a970db9)
 
+![img](https://builds.sr.ht/~vdemeester/home.svg)
 
 
 <a id="h:0272c5ac-0b7f-4ebb-91f0-defa66c2d285"></a>
@@ -41,7 +42,7 @@ dramatically or even not working anymore 😛.
 You should be able to run the `bootstrap.sh` script as is. And if you feel adventurous,
 you can use `curl` for this.
 
-    curl https://gitlab.com/vdemeester/home/-/raw/master/bootstrap.sh | sh
+    curl https://gitlab.com/vdemeester/home/-/raw/master/hack/bootstrap.sh | sh
 
 Otherwise, clone this repository somewhere, read the `bootstrap.sh` file and execute it if
 you feel safe
@@ -74,7 +75,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](#org892ed15).
+-   `docs`: holds documentation about this code, literate configuration, see [literate configuration](#orgf5cfe83).
     `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
@@ -84,7 +85,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="org892ed15"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="orgf5cfe83"></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).
diff --git a/config.nix b/config.nix
@@ -1,8 +0,0 @@
-{
-  allowUnfree = true;
-  packageOverrides = pkgs: {
-    nur = import (builtins.fetchTarball "https://github.com/nix-community/NUR/archive/master.tar.gz") {
-      inherit pkgs;
-    };
-  };
-}