webapp.mk
Features

Backups and portability

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.

Backups and portability

How it works

  1. Your data
  2. Backed up on a schedule
  3. Kept on the platform
  4. Restored when you need it
Managed databases

Every 6 hours

on plans that keep backups

App volumes

Daily or weekly

with the Automatic backups add-on

Export

Plain files

secret values never included

Backups and portability

Managed databases

On plans that keep database backups, every database is backed up for you four times a day.

Automatic

At 00:00, 06:00, 12:00 and 18:00 UTC. The latest, one a day for the last three days and one weekly are kept, at most five at a time.

Manual and saved

Take a backup by hand at any time, and save up to three so they stay until you remove them.

Restore or clone

Restore over the database, or clone a backup into a new database to compare first.

  • A safety backup is taken before every restore, and put back if the restore fails
  • Backups stay on the platform and cannot be downloaded

Deleted by mistake

Deleting a database takes a final backup, and it can be restored as a new database for three days.

Backups and portability

Apps and their volumes

With the Automatic backups add-on, everything that keeps data on a volume can be backed up too.

What is covered

PHP apps, WordPress sites, container apps, database servers, Redis and RabbitMQ, object storage, registries and log collectors.

One restore point for the app

A backup covers every volume of the app, so one restore brings the whole app back.

Your schedule

Daily or weekly, compressed by default. The five newest automatic backups are kept, plus one you save yourself.

Back up now

Take a backup whenever you like, for example before an upgrade. A restore replaces every volume with the backup’s contents.

Static sites

A site’s files come from its branch or archive, so the source already is the backup.

Backups and portability

Take it with you

Export a site or a config as a small JSON file. Keep it in your repository, review it in a diff and import it into another account.

.qk-app: a site

Its source, branch or folder and its serving options.

  • Source credentials are left out
  • An imported site gets its address when you give it one

.qk-def: a config

Variables, flags and the names of the log destinations it uses.

  • Secrets and global variables travel as their key, never their value

Values as a file

Export a config’s values as .env, JSON or shell lines for a runtime that cannot use the client. Secret values are masked unless you may reveal them.

Stack files

webappmk stack save writes chosen sites, apps, databases and configs to webappmk.stack.json. stack deploy creates what is missing and updates what changed.

Backups and portability

Who it is for

Site owners

Roll a WordPress site back after a plugin update went wrong.

Developers

A database backup before every migration.

Agencies

Set up a client from a file instead of by hand.

  • Before an upgrade
  • A bad deploy
  • An accidental delete
  • Moving to another account
Backups and portability

What is backed up

Each resource keeps its backups on its own Backups tab, and the command line has the same actions.

ResourceHowNeeds
Managed databasesEvery 6 hours, plus manual and saved backupsA plan that keeps database backups
PHP apps and WordPressEvery volume, daily, weekly or nowThe Automatic backups add-on
Container appsEvery volume of the appThe Automatic backups add-on
Database servers, Redis, RabbitMQTheir data volumeThe Automatic backups add-on
Object storage, registries, log collectorsTheir data volumeThe Automatic backups add-on
Static sitesThe branch or archive is the source; export as .qk-appNothing
ConfigsExport as .qk-def, .env or JSONNothing

Start with a free static site

Add resources when you need them.