The apimeister-photos engine (ami)
Everlock does not implement a photo library from scratch. The image backend embeds [**apimeister-photos**](https://codeberg.org/apimeister/apimeister-photos) — a standalone, stateless media library kn
Documentation
Tag: images
Running multiple image instances
A single Everlock process can host many independent photo libraries at once. Each library is an **image instance**: its own storage, its own hostnames, its own access grants, and its own gallery. This
Private networks: mDNS discovery
On a home or office LAN there is usually no DNS server you control and no public domain — but the image backend is still host-routed, so clients need a hostname that resolves to the box. Everlock solv
Public hosting: DNS vhosts and ACME
This page covers reaching one or more image instances from the public internet: how a DNS hostname routes to an instance, and how Everlock issues and renews a TLS certificate for it automatically. It
Image backend
The image backend is Everlock's HTTP-facing media library. It lets you host one or more image instances from a single Everlock process, route them by hostname, store the original media inside Everlock
Image instance and access reference
This page covers image instances, routing, and access control for Everlock's image service. The underlying media engine is [apimeister-photos](/docs/images/apimeister-photos); running several instance
Getting started: Image backend
This guide walks through a local first run of Everlock's image backend: - start Everlock with one image instance bound to `localhost` - create a user through the admin SSH console - log in to the gall