App library — zeltro install

zeltro install <app> [name] deploys a finished third-party app, fully configured and running, usually in under two minutes. Open it at the address zeltro status <app> prints.

zeltro install grafana       # monitoring dashboards
zeltro install gitea         # self-hosted git
zeltro install n8n           # workflow automation
zeltro install nextcloud     # file hosting
zeltro install --list        # everything available

For scaffolding a project you write, see Frameworks instead. Guess wrong and Zeltro points you at the right command.

What an installer does for you#

Each installer captures one app's quirks once, so you (or your agent) never re-derive them:

• Creates the app's database on the shared service, plus a dedicated database user when the app refuses to run as root
• Generates secrets and app keys
• Writes a compose file wired to Zeltro's shared services instead of bundled databases
• Gives the app a static IP on Zeltro's network, a container name other containers can reach it by, and a published host port (the IP's last number) for the LAN address
• Points the app's own URL at that IP before it first starts (see below)
• Starts the container and waits until it answers over HTTP

The app's own URL#

Most apps need to know their public URL (APP_URL, ROOT_URL, NEXTAUTH_URL and so on), and many redirect you to it or refuse any other address. Zeltro doesn't write /etc/hosts, so the project name isn't a URL your browser can open. Before the app's first start, zeltro install sets that URL to the project's container IP: http://grafana/ becomes http://10.247.177.124/.

The IP is used, not a localhost port, because it works both from your browser on Linux and from other containers on every OS. Apps that check the hostname itself (Nextcloud and ownCloud trusted domains, Kimai, Readeck, ESPHome, Baby Buddy, Healthchecks) accept both the IP and the project name.

A few apps have an address that is part of their permanent identity, so Zeltro leaves it as the project name:

• Mastodon keeps LOCAL_DOMAIN and WEB_DOMAIN as the name, and lists the IP in ALTERNATE_DOMAINS so it answers there. Its home and explore pages load at the IP, but Mastodon assumes HTTPS in production: its cookies are marked Secure, which a browser won't send over plain http://, and some redirects (sign-up to sign-in, for example) point at https://. To sign in, you need HTTPS in front of it.
• Lemmy keeps hostname in lemmy.hjson as the name. Its web UI talks to the API at the IP.
• Pixelfed is the exception: it serves pages only on APP_DOMAIN, so that is set to the IP.

Newer installers pin image tags to specific versions, not :latest, so an install that worked yesterday works the same today and upgrades are deliberate. Some older installers still use floating tags; see Available apps.

Options#

zeltro install livewire sign-tools
zeltro install livewire sign-tools --image canebaycomputers/cbc:nginx-php8-vector

Removing an app#

zeltro remove grafana                    # stop it and trash the files; data is kept
zeltro remove grafana --force-db-delete  # also drop its databases, DB users and volumes

--force-db-delete drops what the app actually uses, not a database named after the project. It reads the database names and users from the project's compose and .env files, and from the CREATE DATABASE / CREATE USER lines of the installer that created it. So removing zeltro install freescout helpdesk drops the freescout database and the freescout MariaDB user. A database or user that another project's files also name is kept, and the output says so.

Keeping installers current#

zeltro update-installer <app>     # refresh one against current upstream, via AI
zeltro update-installer --all
zeltro create-installer "<idea>"  # write a brand-new installer, via AI

Both emit a prepared prompt telling an agent to fetch upstream, diff against the current installer, regenerate, verify end-to-end, and commit.

Available apps#

There are 214 apps. Being straight about what has and has not been checked, because "200+ apps" is easy to say and hard to stand behind:

• 125 have been installed on a real machine, checked over HTTP, and removed — 114 added in the 2026-08 catalogue expansion, plus 11 older ones spot-checked since. Every one of those pins its images to specific versions.
• 89 are older entries that predate that process. They were written and used, but have not been through it, and most still track floating tags like :latest. They may well work; nobody has recently proved it.

If an older app misbehaves, say so — that is the fastest way for it to get fixed.

Spotted a mistake? Edit this page on GitHub.