Skip to Content

System Status

The System Status tab shows your instance’s storage usage and lets you set a soft warning limit. It also exposes one-shot maintenance jobs (currently the photo dimension repair).

What you see

MetricSource
Total storage usedSum of events/active/, events/archived/, thumbnails/, uploads/
Archive storageevents/archived/ only (your backups proper, separate from gallery photos)
Disk total / free / availablefs.statfs() on the storage path (or container mount)
Recommended soft limit80 % of disk_available if disk metrics look reliable

If your container runs on virtualised storage (some Docker volume drivers, network mounts) the disk metrics may be inaccurate or missing. In that case use the override settings below to give PicPeak a sensible value.

Soft limit

SettingDefaultWhat it does
Storage soft limit (GB)(none)Advisory only. Galleries are not deleted when the limit is exceeded — admins are warned in the dashboard banner and on event creation.

The limit is intended to prompt you to archive old galleries before you run out of disk, not as a hard quota.

Capacity overrides

When the auto-detected disk metrics are wrong (containerised setups, network filesystems), set explicit values here:

SettingDefaultWhat it does
Total capacity override (GB)(auto from fs.statfs)Forces the “disk total” metric to this value.
Available override (GB)(auto from fs.statfs)Forces the “disk available” metric to this value.

Environment-variable equivalents take precedence over the database values. From .env:

STORAGE_CAPACITY_OVERRIDE_GB=500 STORAGE_AVAILABLE_OVERRIDE_GB=120

(Or *_BYTES for exact byte counts.)

Photo dimension repair

PicPeak stores width and height for every photo so masonry and justified layouts can compute aspect ratios. Photos uploaded before this column existed (very early installs), or photos imported via S3 prefix walker before metadata extraction was added, may have null dimensions.

Click Repair photo dimensions to scan every photos row with null width/height and re-extract from the file. Read-only progress: the button shows current count + total. Safe to run anytime; it only writes when a value actually needs filling in.

Photo credits from EXIF

New photos get their credit when they are added. Read Credits from EXIF does the same for photos added before that: it reads EXIF Artist, then XMP dc:creator, then the name inside Copyright, and writes what it finds. It never touches a guest upload or a name you set by hand, and it skips archived events, whose originals are inside the archive.

The card counts photos with a credit and photos not read yet. Files that carry no name stay in “not read yet”, so the button stays available; running it again only re-reads them. Needs the system.manage permission, like the other maintenance jobs on this tab.

Tile placeholders

While a gallery tile’s thumbnail loads, the tile shows a blurred placeholder of the photo (average colour and rough shapes) instead of an empty box. New uploads get their placeholder when the thumbnail is generated. Photos added before placeholders existed have none until you run the backfill.

The Tile Placeholders card counts photos with a thumbnail, how many have a placeholder and how many do not. Compute Placeholders fills the missing ones. It reads only the stored thumbnails, never the originals, and works in batches in the background. The last run’s result shows how many were computed and how many thumbnails could not be read; an unreadable thumbnail stays counted as missing, so the button stays available. Needs the system.manage permission.

On the beta channel from v3.171.0-beta.0; not on stable (v3.134.x). See Release Channels.

Update notifications

The dashboard shows the latest available beta or stable version (fetched from GitHub releases) and a Update Now button that downloads the latest Docker image and recreates the container. The check runs every 6 hours on the backend. There is nothing to configure on this tab — the version-check service is enabled in code.

The “Update Now” button only works when PicPeak is running under a supported container manager. For native installs and orchestrators (Kubernetes, Nomad), follow your normal deploy flow — the button will fail with a “no compatible runtime detected” message.

Last updated on