PhotoPrism

Upstream source: Current installation guide. MariaDB stores the index; the Service volumes store photo originals and generated files. Back up the database and both volumes together.

Towbar manifests

id: photoprism-mariadb
name: PhotoPrism MariaDB
type: mariadb
container:
  network: application
  networkAlias: photoprism-mariadb
  resources:
    cpus: 1
    memory: 1g
secrets:
  runtime:
    - MYSQL_ROOT_PASSWORD
    - MYSQL_DATABASE
    - MYSQL_USER
    - MYSQL_PASSWORD
environments:
  production:
    server: 192.0.2.10

id: photoprism
name: PhotoPrism
buildServer: null
deployment:
  type: image
  image: photoprism/photoprism:250707
container:
  port: 2342
  network: application
  volumes:
    - name: originals
      mountPath: /photoprism/originals
      initialData: image
    - name: storage
      mountPath: /photoprism/storage
      initialData: image
environments:
  production:
    server: 192.0.2.10
rollout:
  type: recreate
  maintenanceMode: true
  reason: Persistent application data uses a single writer
secrets:
  runtime:
    - PHOTOPRISM_ADMIN_PASSWORD
    - PHOTOPRISM_DATABASE_DRIVER
    - PHOTOPRISM_DATABASE_SERVER
    - PHOTOPRISM_DATABASE_NAME
    - PHOTOPRISM_DATABASE_USER
    - PHOTOPRISM_DATABASE_PASSWORD
domains:
  primary: photoprism.example.com
tls:
  mode: direct

Configure

Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration.
Save the initialization values in the table below for the mariadb Datastore under Datastore → Settings → Secrets. Deploy it first and wait for readiness. These values create the database and user only on an empty volume.
Set the Service’s declared runtime values under Service → Settings → Secrets using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
Deploy the Service, then perform the checks below before enabling auto-deploy.
After deployment, transfer a test photo to the server and use docker cp to place it under /photoprism/originals in the running container. The named originals volume retains it across redeployments.

Datastore values

Save these in each Datastore’s Settings → Secrets before deploying it. Use the suggested names or choose your own, then use the same names and passwords in the Service connection values below.

Datastore	Key	Suggested value
PhotoPrism mariadb	`MYSQL_DATABASE`	photoprism
PhotoPrism mariadb	`MYSQL_USER`	photoprism
PhotoPrism mariadb	`MYSQL_PASSWORD`	Run `openssl rand -hex 32`; save its output and reuse it in the Service connection value.
PhotoPrism mariadb	`MYSQL_ROOT_PASSWORD`	Run `openssl rand -hex 32` again for a separate root password.

Runtime values

Save these values on the Service after the repository sync. The manifest declares required keys, not their values.

Key	Value to save
`PHOTOPRISM_ADMIN_PASSWORD`	Generate a unique initial administrator password.
`PHOTOPRISM_DATABASE_DRIVER`	mysql
`PHOTOPRISM_DATABASE_SERVER`	photoprism-mariadb:3306
`PHOTOPRISM_DATABASE_NAME`	Same value as MYSQL_DATABASE.
`PHOTOPRISM_DATABASE_USER`	Same value as MYSQL_USER.
`PHOTOPRISM_DATABASE_PASSWORD`	Same value as MYSQL_PASSWORD.

Verify

Import a small album into /photoprism/originals, index it, and verify both originals and thumbnails survive redeployment. For field constraints, see Service manifest and Datastore manifest.

Start here

Open-source software

Service recipes

Datastore recipes

Complete stacks

Towbar manifests

Configure

Datastore values

Runtime values

Verify

​Towbar manifests

​Configure

​Datastore values

​Runtime values

​Verify

Towbar manifests

Configure

Datastore values

Runtime values

Verify