How a release works: review, install, verify

A release is one version of your application, installed in a place where it runs. Every release reaches Preview or Stage the same way: you review it, LobLogix installs it, and LobLogix confirms that it is running. You manage no servers along the way.

This page describes the alpha. Labels on the Deployment page may change.

What can be released

Only a version that passed your locked checks. The version installed is the exact one that passed, not a rebuilt copy. LobLogix enforces this itself, so no screen or shortcut gets around it. See How checks are run, and what a pass means.

1. Review

Before anything is installed, the Deployment page shows you:

• What changes. The difference between what is running and the new version, in the words of the list you agreed.
• The check results, and any known limits.
• What it does to your stored records. See Changes to your stored records.
• Where it will run. The place is named, so Preview is never confused with Stage.

LobLogix also checks that the place is ready: its database, its capacity, and that nothing else is being installed there. Anything that blocks the release is named, with the next step beside it.

2. Confirm

An Admin or an Editor confirms the release for that place. Nothing is installed without that.

3. Install

LobLogix applies the changes to stored records first, as a step of its own. Then it starts the new version.

4. Verify

A release counts as installed only when the expected version is running and answers a health check. A finished build is not enough. You then get a receipt: the place, the version, the time, and what was verified.

If a step fails

The failed attempt and its output are kept, and the last release that worked stays on record. See If a release goes wrong.

What you never have to do

Rent servers, open a cloud account, copy files or run scripts. For the buttons themselves, see Build and deploy.