Skip to content
TaktSignal

Docs / Look after it · Community Alpha

Updates

TaktSignal never updates itself silently and never checks for updates on its own.

Checking

Control Center → Updates → Check for updates. This is the only moment TaktSignal contacts the TaktSignal release server. It sends a plain request for the list of releases — no installation ID, no ERPNext address, no factory data, not even your version number. Like any web request, the release server sees your computer's internet address.

The list of releases (the release manifest) is signed with the TaktSignal release key. An update is offered only if the signature is valid, the version is newer, it is for the same release channel (Community Alpha) and your computer, and your installed version can update in place. Downgrades are never offered.

Installing

Click Install update (and read View changes first if you like). TaktSignal then:

  1. downloads the update and checks its size and SHA-256 against the signed release list;
  2. checks every file inside it against the list of files the release was built with;
  3. backs up your data (before update);
  4. stops, switches to the new version and starts it, applying database updates;
  5. waits up to three minutes for everything to be healthy.

If an update fails

  • Download or verification failed: nothing was installed; you keep running the current version.
  • The new version does not start: TaktSignal switches back to the previous version automatically and tells you (The last update was undone). If the new version had already changed the database structure, TaktSignal stays stopped and asks you to restore the before update backup (Backups → Restore) — it never starts an older version on a newer database.

Updating with the installer instead

Downloading a newer installer from taktsignal.cloud/download and installing it over the existing one also works; your data is kept. On macOS, a freshly downloaded copy needs the one-time approval again (macOS guide).

Offline

Everything except reading ERPNext and checking for updates works without internet.

In-app updates (including automatic rollback) have been tested on Linux. They are offered only once a signed release server is configured for your build; until then the Updates tab says to download new versions from the website.