Self-host Photoview with Levelrail

A fast, simple photo gallery that indexes an existing folder tree without importing or duplicating files.

  • Authorphotoview
  • LicenceAGPL-3.0
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host Photoview

  1. Pull the images

    One image is pulled on your server.

    Show images
    • photoview/photoview:2.4.0
  2. Create the app

    One service starts in a single Compose app, with 3 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    4 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Photoview requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
AGPL-3.0, network copyleft (agpl) license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Photoview. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Photoview docs page.

Deploy Photoview your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Photoview from the CLI

levelrail-cli templates deploy photoview --name my-photoview

Deploy Photoview with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/photoview/deploy

Photoview configuration

Photoview services

ServiceImagePortsVolumes
photoview photoview/photoview:2.4.0 80 photoview_data -> /dataphotoview_photos -> /photosphotoview_cache -> /app/cache

Photoview environment variables

VariableServiceValue
PHOTOVIEW_DATABASE_DRIVER photoview Preset by the template
PHOTOVIEW_LISTEN_IP photoview Preset by the template
PHOTOVIEW_LISTEN_PORT photoview Preset by the template
PHOTOVIEW_SQLITE_PATH photoview Preset by the template

Ports and volumes

Ports
80
Volumes
3 named mounts: photoview_data -> /data, photoview_photos -> /photos, photoview_cache -> /app/cache

Photoview FAQ

How much memory does Photoview need?

The catalog lists about 256 MiB of memory for Photoview.

Does Photoview run on arm64?

For Photoview, an arm64 image is published; amd64 is image published.

What licence is Photoview under?

Photoview is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.

Does Photoview need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Photoview use?

Photoview listens on port 80 inside the stack.

Where does Photoview keep its data?

In named volumes: photoview_data mounted at /data, photoview_photos mounted at /photos and photoview_cache mounted at /app/cache.

Can I deploy Photoview on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Photoview, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image photoview/photoview:2.4.0 is what you deploy there.

levelrail-cli templates deploy photoview --name my-photoview