Every release can be taken back with one command

The app goes out with one command and comes back with another. Each release is built on the server from a tagged copy of the code, with its libraries locked and scanned for known faults.

Before it switches, every change to stored records is rehearsed on a copy of the records. If the rehearsal fails, or a job is running, or the disk is short, the release stops and the old one keeps serving.

After it switches, it checks that the app answers. If anything is wrong, the back command puts the earlier release in place and reverses its record changes.

Every build note