Module Catalog

What is on this page

Everything is under Module Catalog in the sidebar, split into two screens:

• Built-in — what came with the app. These can be turned off or rolled back to the bundled version, but never deleted.
• Add-ons — modules that are installed when needed, downloaded from straimer.com.

Module updates are not here — they are on Settings → Updates, in the Modules block.

Turning a module on and off

The switch is on the module's card in the catalog. Off means the module's background work stops.

A module installed for the first time starts switched on.

Install refused

The message names the reason. The common ones:

• The module needs a newer Core API — update strAImer. The module is newer than the app. Update the app first, from Settings → Updates. An incompatible module shows "Incompatible — update the app" instead of an Install button.
• The package checksum does not match / the signature is invalid. The download was damaged or replaced, and installation was refused on purpose. Try again; if it repeats, report it — nothing was installed, so nothing is broken.
• Could not download the package / The module registry is unavailable. Our server or the connection. Everything already installed keeps working.

Add-ons shows nothing

Without a connection to straimer.com the list of available modules cannot be shown, and the screen says so. This does not affect installed modules — they are read from the local database and keep working. Built-in stays fully populated.

The catalog caches its answer for about a minute, so right after losing connection it may still look normal.

Uninstalling

Only Add-ons can be uninstalled, with the bin icon. It asks first, and it means it: the module's settings and stored platform access go with it, and that cannot be undone.

Built-in modules have no bin. What they have instead is Restore bundled version, which throws away an update and returns the version that came with the app.

Rolling back a module

The app keeps the two most recent packages of each module, so Roll back is available after at least one update. A copy that has never updated anything has nothing cached and says so.

An update exists on the site but is not offered

Two ordinary reasons:

• The new version needs a newer application. The module then appears under Require a newer app version on the Updates page — update the app first.
• The module belongs to a bundle. Bundle members are updated as a set, and their card says "updates with its bundle" instead of showing a button.

Bundles

Bundles exist only in Add-ons: one card instead of a pile of related modules. They install one after another, and if one fails the rest still install — the failures are listed at the end.

The line under the name says where the bundle stands: 9 modules in one install before anything is there, Bundle 1.0.0 · 9 modules once the whole set is in, and fully installed (9 modules) for bundles that have no releases of their own yet.

Only part of it is installed

If some of the set is missing, the card says partially installed: 2 of 9 and the button becomes Complete install — it fetches what is missing and leaves alone every member that is already on the version the bundle expects. The bin is there as well: a partly installed bundle can be removed like a whole one, since its modules do not work apart.

The count is made from files on disk, not from records in the app. A machine that has received settings from a backup holds a record of every module and none of the files, and the bundle is counted as not installed — which is the truth: there is nothing there to run.

The switch only reaches modules that are actually installed. While part of the set is running it reads 2 of 9 running, and one press always takes the whole bundle to one state. Turning on a partly installed bundle starts what is here and then says Some modules are not installed here: "N module(s) of this bundle are not on this computer. Their settings are already restored — install the bundle and they will be picked up."

The set matches no release

Installing, updating or rolling back members one by one leaves a combination nobody tested together. The card then says Composition changed by hand — does not match bundle 1.0.0 and offers Restore the bundle composition, which puts every member on the version that release fixed.