laurayka/garden
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 19 Wiki Activity

how the site works
All checks were successful
Deploy Quartz site to Pages / build (push) Successful in 38s
Details

Browse Source
This commit is contained in:
Eau
2026-04-12 02:20:38 -05:00
parent 2fd90af200
commit 7799aa971e
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.obsidian/plugins/hoarder-sync/data.json vendored
View File

@@ -4,7 +4,7 @@
"syncFolder": "KaraKeep", "syncFolder": "KaraKeep",
"attachmentsFolder": "KaraKeep/attachments", "attachmentsFolder": "KaraKeep/attachments",
"syncIntervalMinutes": 60, "syncIntervalMinutes": 60,
"lastSyncTimestamp": 1775974816450, "lastSyncTimestamp": 1775978416433,
"updateExistingFiles": false, "updateExistingFiles": false,
"excludeArchived": true, "excludeArchived": true,
"onlyFavorites": false, "onlyFavorites": false,

1
how the site works.md Normal file
View File

@@ -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.