What Stayed Local In The Photography Workflow

Photography

The first photography-server experiment answered a storage question: could I turn three USB drives, Proxmox, and TrueNAS into a useful working archive?

The next question was less technical. Which parts of a photography business actually belonged on that machine?

It was tempting to keep adding services because the hardware was already running. Client galleries, booking, contracts, invoicing, CRM, and the public portfolio could all be self-hosted in theory. In practice, sharing a machine does not make those workloads a coherent system.

The Archive Has Different Needs

RAW files, edited masters, and print exports are large, private, and expensive to replace. They benefit from local network speed, snapshots, checksums, and storage I can physically account for.

That made the TrueNAS side straightforward:

  • Keep master photography and working files local.
  • Expose them to editing machines over SMB.
  • Use ZFS scrubs, snapshots, and monitoring.
  • Treat RAIDZ1 as fault tolerance, not backup.
  • Preserve an independent-copy requirement.

The USB enclosure still imposed an uncomfortable compromise. Disabling UAS and autosuspend made it more predictable, but it did not turn consumer USB bridges into enterprise storage hardware. That limitation belongs in the operating plan, not in the fine print.

Clients Should Not Need My Network

A gallery or booking page has the opposite access pattern. It must be reachable from anywhere, load without a VPN, and remain available when the local ISP or lab is being maintained.

Those functions belong on public hosting or a service designed for client delivery. Contracts and invoices may be better handled by established SaaS products. Internal administration can stay private, but only if remote access is deliberate and supportable.

This produced a hybrid workflow rather than a self-hosting purity test:

local storage        public delivery
RAW masters          portfolio
edited masters       client galleries
working files        booking and contact
internal tools       selected final exports

Final images can move outward. The archive does not need to move with them.

The Machine Did Not Define The Architecture

The useful boundary was ownership and access, not whether an application could run in a VM.

I want the irreplaceable files close enough to control and the client experience far enough away that it does not depend on my local network. The home lab earns its place by doing the storage-heavy private work well. Public systems earn theirs by being boring to reach.

That division is less exciting than putting an entire business in one rack. It is also easier to explain, recover, and live with.