how the site works

minor version increment [skip actions]
2026-04-12 02:21:14 -05:00 · 2026-04-12 07:16:06 +00:00
3 changed files with 3 additions and 2 deletions
--- 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,
--- a/works.md
+++ b/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.
--- a/version.txt
+++ b/version.txt
@@ -1 +1 @@
-1.13.0
+1.14.0
Author	SHA1	Message	Date
Lauren Kaviak	7799aa971e	how the site works All checks were successful Deploy Quartz site to Pages / build (push) Successful in 38s Details	2026-04-12 02:21:14 -05:00
Build Pipeline	2fd90af200	minor version increment [skip actions]	2026-04-12 07:16:06 +00:00
				`@@ -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.
@@ -1 +1 @@
 .13.0
 .14.0