Commit ed3e7e62d296

@@ -1,6 +1,8 @@
 image: fedora/latest
+secrets:
+  - 67527e1f-d69c-4f8e-a26d-21685f4ed380
 sources:
-  - https://gitlab.com/vdemeester/home.git
+  - git@git.sr.ht:~vdemeester/secrets
 tasks:
 - hello: |
     echo "do something with fedora at some point"

@@ -1,8 +1,9 @@
 image: nixos/20.03
-sources:
-  - https://gitlab.com/vdemeester/home.git
 secrets:
+  - 67527e1f-d69c-4f8e-a26d-21685f4ed380
   - 0818d60d-b587-4d4e-81d8-dc15072ccb97
+sources:
+  - git@git.sr.ht:~vdemeester/secrets
 tasks:
 - pkgs: |
     set -euo pipefail

@@ -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](#org6f7fd26).
+-   `docs`: holds documentation about this code, literate configuration, see [literate configuration](#org3f3a0bc).
     `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="org6f7fd26"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="org3f3a0bc"></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).