Virtual hosts
Every HTTP backend serves on virtual hosts: the names clients put in the URL. One vhost carries several backends at once — a calendar, an address book, a file share and a website on `jens.dev`, for ex
Documentation
Tag: http
Routing and content negotiation
How a Markdown-mode site turns a request path into content, and how the same page can answer with either HTML or its Markdown source. These are answered before any file lookup: | URL | Response | |---
Git over HTTP
Repositories are served over HTTPS as well as SSH, using git's standard smart HTTP protocol. Clone, fetch and push work with an unmodified git client. One backend serves three things on one host: the
Admin over HTTP
The `backend-admin-http` outlet serves two surfaces on its pinned vhost: the web dashboard at `/admin` and the HTTP API at `/api`. Both run every action through the same command engine as the SSH cons
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