Lerd Service Store

The community-driven store of service presets that powers Lerd — add a database, cache, search engine, or admin dashboard by editing YAML, no binary release required.

Run lerd service search, pick something, lerd service preset <name> — and Lerd pulls the matching preset from this store, then knows exactly how to run it: which image and ports, how to wire your project's .env, which admin dashboard to embed, what it depends on, and which config files to mount for auto-login. Everything is a single YAML file. Add a service here and every Lerd install can use it within 24 hours, with no new Lerd release and no Go code.

That's the whole point: Lerd ships only the default stack — MySQL, PostgreSQL, Redis, Meilisearch, RustFS, Mailpit — and every other service lives here. MongoDB, MariaDB, phpMyAdmin, pgAdmin, Elasticsearch, RabbitMQ, and whatever you add next are all defined in this repo, not hardcoded in the binary.

What a preset powers

A single <name>.yaml teaches Lerd to:

• 📦 Run the container — image, ports, volumes, and environment, wired into a rootless Podman quadlet
• 🌱 Wire your .env — inject the host, port, and credentials your framework expects, with auto-detection
• 🖥️ Embed a dashboard — phpMyAdmin, pgAdmin, RedisInsight and friends open inside the Lerd UI, already logged in
• 👪 Group into families — alternates and admin UIs discover every installed family member automatically
• 🔢 Offer versions — ship multiple selectable image tags; every member shares the family's canonical host port and Lerd shifts collisions for you
• 🔗 Declare dependencies — pull in the services a preset needs, started in order
• 📄 Mount config files — static files inline, or dynamic ones (like pgAdmin's discovered server list) via a built-in generator

All of it is data. None of it ships in the binary.

Available services

Databases

Service	What it is
clickhouse	ClickHouse column-oriented analytics database, with its own SQL console
mariadb	MariaDB, the MySQL-compatible server (multi-version)
mongo	MongoDB document database
postgres-pgvector	PostgreSQL + pgvector for vector search (multi-version)
postgres-timescaledb	PostgreSQL + TimescaleDB for time-series (multi-version)

Admin dashboards — open inside the Lerd UI, auto-logged-in

Service	For
phpmyadmin	every installed MySQL / MariaDB service
pgadmin	every installed PostgreSQL service
mongo-express	MongoDB
redisinsight	Redis
elasticvue	Elasticsearch
typesense-dashboard	Typesense
opensearch-dashboards	OpenSearch

Search & analytics

Service	What it is
elasticsearch	Elasticsearch single-node engine
opensearch	OpenSearch single-node engine
typesense	Typesense typo-tolerant search

Cache, queues & messaging

Service	What it is
valkey	Valkey, the Redis-compatible cache (coexists with Redis)
memcached	Memcached in-memory cache
rabbitmq	RabbitMQ broker with management UI
soketi	Pusher-compatible WebSocket server
beanstalkd	Beanstalkd work queue

Testing & tooling

Service	What it is
selenium	Headless Chromium with a noVNC viewer for browser tests
stripe-mock	Stripe API mock server
gotenberg	Gotenberg API for PDF and document conversion

Don't see what you need? Add it — that's what this repo is for.

Usage

You rarely touch the store directly: everything routes through the usual service commands.

lerd service search                  # list everything available
lerd service search search-engine    # search by name, description, or family
lerd service preset phpmyadmin        # install a preset (fetched on demand)
lerd service preset mariadb --version 11.8   # pick a version on multi-version presets

Installed presets are cached locally and auto-refresh every 24 hours, so improvements landed here reach existing installs without an update.

Contributing

New services and version bumps are welcome — this store is only as good as the community around it.

1. Fork this repo
2. Add or update services/<name>.yaml
3. Optionally add the service's own mark as services/<name>.svg (see below)
4. Add or update the matching entry in services/index.json (name, description, and optionally family, dashboard, depends_on)
5. Open a pull request

Keep images pinned to a specific tag or a track_latest family; avoid :latest for anything that stores data.

Preset schema

Definitions live under services/: an index.json catalogue plus one <name>.yaml per preset. A minimal preset:

name: my-service
image: docker.io/example/my-service:1
description: What it is
ports:
  - "8099:80"

Common fields build on that:

family: my-family          # group alternates + dashboards for auto-discovery
versions:                  # multi-version family (all share the canonical port)
  - tag: "2"
    image: docker.io/example/my-service:2
    canonical: true
env_vars:                  # keys injected into the project .env
  - MY_HOST=lerd-{{name}}
dynamic_env:               # computed at install time (e.g. family discovery)
  MY_HOSTS: discover_family:my-family
depends_on:                # started first
  - mysql
dashboard: http://localhost:8099
files:                     # config-file mounts (static content, or a generator)
  - target: /etc/my-service/config
    content: |
      key = value
introspect:                # database engines only: power the web UI Databases tab
  list_databases: >        # print one "name<TAB>size_bytes" row per user database
    psql -U postgres -tAc
    "SELECT datname || chr(9) || GREATEST(pg_database_size(datname)
    - (SELECT pg_database_size('template1')), 0) FROM pg_database
    WHERE datistemplate = false AND datname <> 'postgres' ORDER BY datname"
extensions:                # postgres engines only: what the image can create
  - name: vector           # created wherever Lerd creates a database
    always: true
    types: [vector]        # a dump naming one of these brings the extension with it

How a preset appears in the dashboard

Three fields decide that, and all three live here rather than in lerd, so a new service looks right the day it lands:

category: databases    # discovery section: databases, cache, messaging, search,
                       # mail, admin, storage, testing, other
icon: database         # one of lerd's built-in glyphs
color: "#003545"       # the brand colour its mark is tinted with

color must be a plain hex literal, #003545 or #abc. Anything else, a colour function or a CSS variable, is dropped and the service falls back to its category's tint. A colour too dark to read on lerd's dark card, or too light for the light one, is nudged toward the card until it separates, so a near-black brand still shows up.

Shipping a service's own mark

icon can only borrow a glyph lerd already ships. To give a service its actual logo, add services/<name>.svg next to its YAML. lerd fetches it with the definition and caches it, so it reaches existing installs on the same 24 hour refresh with no lerd release, and the dashboard serves it from that cache rather than from here, which keeps it drawing offline.

The mark is monochrome: one silhouette of filled paths with no colours of its own, tinted at render time by color. It renders at 20 px beside lerd's built-in glyphs and has to work on a light and a dark card, so a full-colour brand mark is not what this is for, and neither is a wordmark, which turns into a smear at that size. Take the logo, not the lockup.

That markup is inlined into the dashboard, so lerd cuts it down on the way in. Only svg, g, path, circle, ellipse, rect, line, polyline and polygon survive, keeping their geometry alone: script, foreignObject, event handlers, external references, and any fill, stroke, style, class or id are stripped, as is anything over 32 KB. Keep the file to a bare <svg viewBox="…"> around its paths and nothing is lost:

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="…"/></svg>

A file lerd refuses is simply not cached, and the service falls back to the glyph its icon names. The marks currently in this repo come from Simple Icons, which is CC0.

Ship a mark only when it is the service's own. An admin UI has no business borrowing the engine's: Mongo Express drawing the Mongo leaf in Mongo green makes the two tiles indistinguishable, where falling back leaves it on the admin tint and readable as the separate thing it is. phpMyAdmin ships a mark because it has one of its own.

A family is the other way round. Every member of one is that engine, so they all carry its mark and its colour: pgvector and TimescaleDB are Postgres, and both draw the Postgres elephant in Postgres blue rather than a mark of their own.

See the service presets documentation for the full schema reference and every available field.

License

MIT