Variables
Plain keys and values, such as PORT or LOG_LEVEL.
Keep variables, secrets and feature flags out of your code. Your app fetches them when it starts, wherever it runs, and changes reach it without a redeploy.
Environment
or a .env or JSON file
~30 seconds
while the client watches
5 to 20
on every paid plan
A config is a named set of values for one application. Edit it in the control panel, from the command line or through the API.
Plain keys and values, such as PORT or LOG_LEVEL.
Stored encrypted and masked in the panel. A variable points at a secret by its key, so the value lives in one place.
Values your account uses in many configs, such as a region or an API address. Change one and every config that points at it follows.
On and off switches your code reads, flipped without a deploy.
Attach a log destination and the client ships your app’s output there.
Paste a .env or JSON to fill a config. Export it as .env, JSON or shell lines, or as a .qk-def file to commit next to your code.
webappmk-client is one small static binary for Linux. It reads three settings, fetches the config and starts your application.
The client fetches the config and replaces itself with your application, which sees every value as an environment variable.
For software that only reads a .env or a JSON file.
Started with run or serve, the client checks for changes about every 30 seconds. With exec, a change arrives on the next start.
Make one fetch key for production, one for CI and so on. Each is shown once and stored hashed. Revoke one and the others keep working.
One config for every environment, with secrets out of the repository.
Rotate a database password in one place and every app picks it up.
Configure apps on your own servers or cluster from the same panel.
The control panel shows these steps with your address, config name and key filled in, for a host, Docker, Compose and Kubernetes. Your image does not change.
curl -fsSL <config-address>/v1/install.sh | sh
export WEBAPP_MK_URL=<config-address>
export WEBAPP_MK_INSTANCE=my-api
export WEBAPP_MK_SECRET=<fetch-key>
webappmk-client exec -- ./your-appwebappmk-client write --format dotenv --out .env
# or JSON
webappmk-client write --format json --out config.jsondocker run \
-v webappmk-client:/wmk:ro \
-e WEBAPP_MK_URL=<config-address> \
-e WEBAPP_MK_INSTANCE=my-api \
-e WEBAPP_MK_SECRET=<fetch-key> \
--entrypoint /wmk/webappmk-client \
your-image:tag exec -- ./your-appRun any Docker image with a private network, persistent volumes and a port on your domain.
Send the access logs of your sites and the output of your apps to a log collector that runs on your realm, or to your own Loki or HTTP endpoint.
Automatic backups for databases and for the volumes of your apps, restores you start yourself, and files that carry a site or a config to another account.