blumeops/docs/reference/storage/sifaka.md
Erich Blume 7983677da2 Fix wiki-links to use filename-based resolution
Quartz's "shortest" path mode resolves wiki-links by filename, not
frontmatter title. This fixes the broken links from the previous
title-based approach.

Changes:
- Rename zk duplicate files with -log suffix to avoid conflicts
- Rename reference/storage/postgresql.md to postgresql-storage.md
- Convert all wiki-links from [[Title]] to [[filename|Title]] format
- Rename doc-card-titles task to doc-filenames (checks filename uniqueness)
- Update pre-commit hook for renamed task

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-03 15:27:23 -08:00

1.9 KiB

title tags
Sifaka NAS
storage

Sifaka NAS

Synology NAS providing network storage and backup target.

Quick Reference

Property Value
Dashboard https://nas.ops.eblu.me
Model Synology
Storage 10.9TB RAID 5
Role Backup target, media storage

Network Shares

Share Path Purpose Consumers
backups /volume1/backups Borg backup repository [[borgmatic
torrents /volume1/torrents ZIM downloads [[kiwix
music /volume1/music Music library [[navidrome
allisonflix /volume1/allisonflix Video library [[jellyfin
photos /volume1/photos Photo library [[immich

NFS Exports

Export Allowed Clients Purpose
/volume1/torrents 192.168.1.0/24, 100.64.0.0/10 k8s pods via Docker NAT
/volume1/music 192.168.1.0/24, 100.64.0.0/10 k8s pods via Docker NAT
/volume1/photos 192.168.1.0/24, 100.64.0.0/10 k8s pods via Docker NAT

Monitoring

Node exporter running in Docker container, scraped by prometheus at sifaka:9100.

Tailscale

  • Tag: tag:nas
  • ACL: tag:homelab can access for backups

Backup

Sifaka is the target for backup, not a backup source. borgmatic sends backups TO sifaka, not OF sifaka.

Data protection for sifaka itself currently relies on the Synology RAID 5 configuration, which provides single-disk fault tolerance. Future plans include offsite duplication for additional resiliency.