Skip to content
vops

Install a catalog application

Catalog applications provide pre-built images and a reviewed flui.yaml declaration. They are the shortest path to a service you do not need to build from source.

Browse before installing

Terminal window
vops app catalog
vops catalog products
vops catalog describe uptime-kuma

The catalog view shows what an application is and which values it will ask for. Inspection is local and changes nothing.

Check the host

Terminal window
vops app preflight web-1

If the required application runtime is absent, install it explicitly:

Terminal window
vops app setup web-1 --yes

Render the install plan

Terminal window
vops app install uptime-kuma --host web-1

Without --yes, vops runs the preflight and prints the full plan. Use --set KEY=value for values the catalog entry declares:

Terminal window
vops app install <catalog-id> \
  --host web-1 \
  --set REQUIRED_VALUE=...

Review generated credentials, volumes, ports and whether the application will be loopback-only or publicly exposed.

Install and verify

Terminal window
vops app install uptime-kuma --host web-1 --yes
vops app status uptime-kuma
vops app logs uptime-kuma --lines 200

Add a domain later

An internal application can be exposed after its initial install:

Terminal window
vops app expose uptime-kuma \
  --domain status.example.com \
  --yes

vops ensures the host ingress exists, binds the application behind it and requests TLS when configured. Use --domain auto for a temporary demo hostname; use a domain you control for a stable installation.

Remove without destroying data by default

Terminal window
vops app remove uptime-kuma --yes

Persistent data is a separate concern. The --purge flag also deletes volumes and secrets, so it should be reviewed as a destructive operation rather than a routine uninstall.