From 7799aa971eaeb3757596943d89cfb4153533d1eb Mon Sep 17 00:00:00 2001 From: Lauren Kaviak Date: Sun, 12 Apr 2026 02:20:38 -0500 Subject: [PATCH] how the site works --- .obsidian/plugins/hoarder-sync/data.json | 2 +- how the site works.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 how the site works.md diff --git a/.obsidian/plugins/hoarder-sync/data.json b/.obsidian/plugins/hoarder-sync/data.json index 412527c..52d4f36 100644 --- a/.obsidian/plugins/hoarder-sync/data.json +++ b/.obsidian/plugins/hoarder-sync/data.json @@ -4,7 +4,7 @@ "syncFolder": "KaraKeep", "attachmentsFolder": "KaraKeep/attachments", "syncIntervalMinutes": 60, - "lastSyncTimestamp": 1775974816450, + "lastSyncTimestamp": 1775978416433, "updateExistingFiles": false, "excludeArchived": true, "onlyFavorites": false, diff --git a/how the site works.md b/how the site works.md new file mode 100644 index 0000000..cb64807 --- /dev/null +++ b/how the site works.md @@ -0,0 +1 @@ +This obsidian vault is stored in a git repository on my gitea instance. It has a workflow which clones the quartz v4 repository, installs the dependencies, patches it, copies the vault contents into the relevant quartz v4 repo folder, runs the quartz build command, and tar's the build output as a release. I then have an nginx deployment in my k3s cluster that downloads the latest release tar ball, inflates it and serves it in an nginx server. It's a lot more straight forward than you would think. \ No newline at end of file