backdown update

backdown update [OPTIONS]

Options#

--check

Only say whether there is one (exits 10 when there is); with --from, only verify the folder and change nothing.

--refresh

Ask GitHub now instead of using today's answer.

--rollback

Put back the version the last update replaced.

--channel <CHANNEL>

stable or preview (default: as in Settings; previews while this is a preview).

--json

Print it as JSON, for scripts.

--from <FOLDER>

Install from FOLDER, without a network: it holds this system's release archive, SHA256SUMS.txt and SHA256SUMS.txt.sig, carried over from the release.

--allow-unsigned

With --from: go ahead without SHA256SUMS.txt.sig. The checksums then show only that the files arrived whole, not that they're BackDown's.

--allow-older

With --from: install it even if it isn't newer than this version.

Also takes the global options --db and --local.

Good to know#

Asks GitHub's public list of BackDown releases, only when you run it (or when Settings says to look once a day); the answer is kept for a day. Installing downloads this computer's archive and SHA256SUMS.txt, refuses unless the SHA-256 matches, checks the new program runs, keeps the old one in your data folder, swaps them and restarts the background service; if the new one doesn't start, the old one is put back. A copy installed by a package manager, an AppImage or Homebrew is updated that way instead, and it says so.

Examples#

# is there a newer version? (exits 10 when there is)
backdown update --check
# download it, check it against SHA256SUMS.txt and install it
backdown update
# put back the version the last update replaced
backdown update --rollback

See also#

• Updates