Skip to content

feat(resume): add a volsync-backed blog-content volume and mount it read-only at /app/blog-static - #4952

Open
dapperdivers wants to merge 1 commit into
mainfrom
blog-content-volume
Open

dapperdivers wants to merge 1 commit into
mainfrom
blog-content-volume

Conversation

@dapperdivers

Copy link
Copy Markdown
Owner

Storage for derekmackley.com/blog. Posts are kept out of git and out of the portfolio image: a publisher job (follow-up) writes the built static site to this volume, and the site serves it.

What's added

  • blog-content Kustomization using the shared volsync components, the same pattern as obsidian-second-brain: a 2Gi cephfs-shared ReadWriteMany PVC, daily local + R2 restic backups, and restore if the PVC is ever recreated. Daily is enough because the content can be rebuilt from the vault.
  • The resume pod mounts it read-only at /app/blog-static, which is where the server looks by default (BLOG_PATH). resume now depends on blog-content.
  • No new secrets: the component only uses the shared RESTIC_PASSWORD / R2 keys.

Order
Safe to merge before or after dapperdivers/developer-portfolio#51. Until that image is live the mount is unused; after it, /blog returns a 404 until the publisher writes something.

Checks

  • flux build ks blog-content --dry-run renders the PVC (2Gi, cephfs-shared, RWX), both ReplicationSources (schedule 0 3 * * *), the ReplicationDestination and both ExternalSecrets.
  • pre-commit (oxfmt, gitleaks) passed.

Next: the publisher, a vault-jobs CronJob that builds only allowlisted Projects/Blog notes and writes the output here. Only that job will mount this volume read-write.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant