Installing and Updating Sally

Sally needs no installer. A release is a .zip file for your platform (x64, x86 or ARM64); unpack it to a folder you can write to, for example C:\Tools\Sally, and run sally.exe. Keep the plugins, toolbars and utils folders next to sally.exe. Your settings are kept per user, outside the folder, so an update never touches them.

Sally's updater, utils\salupdate.exe, finds new releases on GitHub and installs them. Sally itself never goes online for updates: it starts the updater.

From Sally 1.0.38, the updater follows the language selected in Sally, including English when Windows uses another language. If no valid Sally language is configured, it chooses an available Windows language, falling back to English. Its windows and confirmation messages use Sally's dialog font and application icon. From 1.0.40, the updater uses your custom panel font when configured, otherwise the Windows dialog font, and follows the saved application icon colour.

To update from Sally:

Choose Help/Check For New Versions. The update window opens, asks GitHub for the latest release, and shows the installed and the latest version with the release notes.
When a newer release is shown, click Install and Restart.
The updater downloads the release, checks it against the SHA-256 checksum published with it, unpacks it and asks you to confirm.
Every Sally window started from the same folder closes, the files are replaced, and Sally starts again. The update window then tells you how the update went.

Open the release page shows the release on GitHub. Nothing is installed unless you click Install and Restart.

Release notes and voluntary support

From Sally 1.0.39, the update window separates What's new from From the maintainer. Signed content can provide notes in your selected language; English release notes remain available when optional content cannot be loaded. Maintainer messages are visible to everyone. Missing content does not prevent a free update.

Help/What's New opens the installed release's bundled notes entirely offline. It does not check for newer versions or install anything. Use Check for Updates there for an explicit online check.

Support Sally opens the financial support page. In 1.0.40, optional support actions appear during update checks and in the compact successful-update confirmation. A voluntary supporter key enables your supporter badge: your chosen name in About and, optionally, Sally's title. During active or future-dated support, the updater hides its support and key-entry buttons. Your name, dates and key management remain available in About; maintainer messages remain visible. Every feature and update stays free. Close simply closes the update window without changing supporter preferences.

Enter supporter key lets you paste a key or import its file. Verification is automatic and offline; check the name and dates, then choose Save key. In About, Supporter details shows your saved name and support dates. The optional title-name checkbox is saved immediately. Use the small arrow beside Close for replacement, export or confirmed local removal. Your name is shown locally on your computer.

After contributing through PayPal or Buy Me a Coffee, use the request link on the support page to email badges [at] get-sally [dot] app with your preferred badge name, delivery address, payment provider and payment name or transaction reference. Keys are issued manually, usually within one week. Every feature and update remains free.

Links in either reading panel can be opened with the mouse or through its context menu: focus the panel and press Shift+F10 or the Applications key.

Automatic update schedule

Sally also looks for a newer release by itself, every week unless you choose otherwise with Check for updates in Configuration/General (from every day to every six months, or never). Nothing is shown unless there is a newer release; then the update window opens without taking the keyboard from what you are doing, and its taskbar button flashes. If GitHub cannot be reached, Sally tries again the next day.

Up to Sally 1.0.36 the Check Version plugin did this. Sally 1.0.37 takes over its schedule and removes the plugin.

To update from a release you downloaded (also offline):

Download the release's .zip file for your platform and, if you can, its Sally-v<version>-SHA256SUMS.txt into the same folder.
Drop the .zip file onto utils\salupdate.exe in your Sally folder, or run utils\salupdate.exe <path to the .zip>.
The updater names the installed and the new version (and asks before installing an older one), says whether Sally is running, and asks once. Sally closes, the files are replaced, and Sally starts again.

The updater's command line

<file>.zip	Installs a release you downloaded (see above).
--yes	Answers every question with Yes and runs without messages; errors are still shown. The outcome is written to the log (see below).
--install <folder>	Updates the Sally in that folder instead of the one the updater is in.
--check	Opens the update window, as Help/Check For New Versions does.
--whats-new	Shows the installed release's bundled notes offline, as Help/What's New does. May be combined with --install to select a Sally folder; online-check and installation-action switches are not accepted with this mode.
--auto	With --check: shows nothing unless there is a newer release, as Sally's own check does. The exit code is 0 when Sally is up to date, 1 when the window was shown, and 2 when GitHub could not be reached.
--feed <address>	With --check: asks another HTTPS address that answers like GitHub's release feed (a mirror).
--report --result <file>	Shows how the update that left the result file went. Sally starts it after an update.

Run salupdate.exe without a file to undo an update that was interrupted, for example by a power failure. Sally starts the updater with further switches of its own (--prepare, --apply and those they take) to install a release; they are not meant to be typed.

What an update changes

Only the files of the release are replaced. Files that are not part of it, such as an exported configuration or files you added, are left alone.
A file an earlier release installed and a newer one no longer has (a plugin that was retired, such as Check Version in 1.0.37) is removed. The release lists such files in sally-update.obsolete in the Sally folder.
Nothing is changed until the new files are ready, and if any file cannot be replaced, every file is put back exactly as it was.
Windows Explorer keeps Sally's shell extension (utils\salextx64.dll, or salextx86.dll or salextARM64.dll) loaded. The updater renames the loaded file aside, for example to salextx64.dll.sally-old, and puts the new one in its place; Sally deletes the old copy at a later start, once Explorer no longer uses it. No restart of Windows is needed.
A Sally folder under Program Files asks for administrator permission once, for replacing the files only.

Before a package is installed, the updater makes sure it is a Sally release for your processor and refuses a package that would write outside the Sally folder. A package that does not match its published SHA-256 checksum is refused; one without a checksum to compare with is installed only after you confirm.

Where to look if something goes wrong

The updater's log and its last result: %LOCALAPPDATA%\Sally\Update\salupdate.log and result.txt. Downloads are kept in the same folder until the update is done.
You can always update by hand: close Sally and unpack the new release over the Sally folder. If Windows reports salextx64.dll as in use, rename that file and copy again.
Sally 1.0.35 and older have no updater; update them by hand once.