Skip to content

Dockup 1.2.0

Choose a tag to compare

@gh-lm gh-lm released this 19 Oct 19:51
· 2 commits to main since this release

Released 2026-10-19.

The release that makes Dockup safe to hand to somebody else, and a pleasure
to use.

  • Dockup is one of its own stacks. It lives in the stacks folder beside
    everything it manages, shows up in its own list, and is opened, read and
    updated exactly like any other container. The one thing a container cannot
    do to itself, replacing its own container, is handed to a short-lived
    helper, so the page goes quiet for a few seconds and comes back on its own
  • Dumps before a backup. A database copied while it is being written to
    often will not restore. Dockup can now ask an application for a clean copy
    of itself, early in the morning, ahead of whatever copies the machine
    overnight, and writes a status file saying when each one was made and
    whether it worked. A dump that fails never replaces a good one
  • Backup and restore you can trust. A backup never contains the earlier
    backups, refuses to be kept if it suddenly doubles in size, and only one
    runs at a time. Restore refuses while stacks are running, swaps each stack
    folder instead of deleting it, keeps the old one beside it, never touches
    Dockup's own folder, and asks again if the backup had to leave files out.
    Export streams from disk instead of holding everything in memory
  • Safer by default. Dockup will not start with a missing, short or
    example secret key, and says why in one line. It cannot be stopped, taken
    down or deleted from its own screen. A backup retention of zero can no
    longer delete every backup. Settings that are numbers are checked when
    saved, and a mistake is shown under the box it belongs to
  • Stacks stop asking to be updated for ever. On a stack with more than
    one service, Dockup compared each service against another service's image.
    Each service is now compared with its own
  • A new look, from the first page to the last. A charcoal page with
    panels that stand clear of it, every screen opening with one plain
    sentence about how things stand, the label on a button appearing as a small
    pill, switches and our own dropdowns instead of the browser's, tables as
    raised rows, a two-panel sign-in page, and a colour picker made of the
    palette itself. Settings save themselves and the box glows briefly. There
    are no pop-up messages, no ticks and no Save button
  • Anything that cannot be undone asks twice. The first click fills the
    button, a second within three seconds does it
  • Installation is the same on any server: a compose file with an obvious
    secret key to replace, and nothing in it that belongs to one machine