Updates

TrailSail updates itself from this website, and it updates the server package for you from the Server panel. Both are signed, and the update check is your choice.

The app

On first launch, after the terms, TrailSail asks one question: Check for updates automatically?

  • Check automatically: once a day TrailSail asks trailsail.app whether a newer version exists. When there is one, it shows what changed and offers to install it. Nothing is installed without your say-so.
  • Don't check: TrailSail never contacts trailsail.app by itself.

Either way you can look whenever you like: TrailSail → Check for Updates… in the menu bar, or Settings → General → Updates → Check now. The switch on that same screen changes your answer.

What the check sends

It is a request for one small file, the update feed. It carries the app's version number and, like any web request, comes from your IP address. Nothing about you, your Mac, your servers or your chats is sent, and this website keeps no analytics.

Why an update can be trusted

Every release is signed with a key only Yard8 holds, and TrailSail carries the matching public key. An update that is not signed by that key is refused, even if it comes from the right address.

Doing it by hand

You can always download the current version from the Download page and drag it over the old one. Your chats and settings are kept.

The server package

The app carries a copy of the server package. When that copy is newer than the one on a paired server, the Server panel says so:

Server package 0.1.0 is installed; 0.2.0 is available. Update to 0.2.0

Pressing the button sends the package over the paired connection. The server checks its signature before installing, so only a package made by Yard8 is accepted. Then it replaces its own command-line tool and control service and restarts the control service.

  • Engines, models, keys, pairings and your licence are kept.
  • Models that are loaded stay loaded; the engines are not restarted.
  • The server never goes to the internet for this.
  • The panel may show "cannot reach" for a few seconds while the control service restarts.

So the usual order is: update TrailSail, then press Update in the Server panel.

The first time

A server installed before this feature existed cannot update itself. Install the current package on it once, from the Download page; after that, updates come through the app.

Engines

Splash, llama.cpp and SearXNG are separate from the package. Settings → Server → ⋯ → Update engines runs their own updates on the server.

Found a problem, or is something here unclear? Report it.