aboutsummaryrefslogtreecommitdiff
path: root/src/content/blog/2019/06/02
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--src/content/blog/2019/06/02/nixos-stateless-workstation.adoc (renamed from _articles/2019-06-02-using-nixos-as-an-stateless-workstation.md)8
1 files changed, 3 insertions, 5 deletions
diff --git a/_articles/2019-06-02-using-nixos-as-an-stateless-workstation.md b/src/content/blog/2019/06/02/nixos-stateless-workstation.adoc
index d78c1d5..c0cfe75 100644
--- a/_articles/2019-06-02-using-nixos-as-an-stateless-workstation.md
+++ b/src/content/blog/2019/06/02/nixos-stateless-workstation.adoc
@@ -1,6 +1,4 @@
----
-
-title: Using NixOS as an stateless workstation
+= Using NixOS as an stateless workstation
date: 2019-06-02
@@ -55,7 +53,7 @@ After this positive experience with recreating my OS from simple Nix
expressions, I started to wonder how far I could go with this, and
started considering other areas of improvements:
-### First run on a fresh NixOS installation
+== First run on a fresh NixOS installation
Right now the initial setup relies on non-declarative manual tasks, like
decrypting some credentials, or manually downloading **this** git
@@ -64,7 +62,7 @@ repository with specific configurations before **that** one.
I wonder what some areas of improvements are on this topic, and if
investing on it is worth it (both time-wise and happiness-wise).
-### Emacs
+== Emacs
Right now I'm using the [Spacemacs](http://spacemacs.org/), which is a
community package curation and configuration on top of