ReleasesController
Corex\Config\Releases\ReleasesController · class · Config layer
The Releases screen’s routes (spec 107, slices 3 and 4). GET releases what is installed, what the host cannot do, the packages here, an installation in progress, or what one left GET releases/uploads/{hash} how much of an upload the site holds POST releases/uploads/{hash} a part of a package, as the request’s body POST releases/uploads/{hash}/complete all of it has been sent: keep it, if it is what was sent POST releases/inspect what a package on the site is, or why it is refused POST releases/install/prepare what installing a package would do, and the way back POST releases/install/confirm the version, typed POST releases/install/step the next piece: unpack, verify, copy tables, swap POST releases/install/finish the database step, answered by the release just installed POST releases/install/cancel give up an installation that has moved nothing POST releases/return go back to the release before, with what confirms it typed POST releases/leftovers/remove remove what an installation left, when none is in progress Only step, finish, return, cancel and leftovers/remove change a file of the site outside wp-content/corex-releases/. cancel changes only the maintenance file and the recovery plugin, for an installation that stopped at the swap; leftovers/remove only the recovery plugin. install/finish is a contract between releases: the release that asks for it is not the release that answers. Its path, that it takes no argument, and the shape of its answer (done, version, changes, or where the installation stands) stay as they are for as long as a release that speaks ReleaseProgress::PROTOCOL 1 can be installed over.