ReleaseLeftovers
Corex\Config\Releases\ReleaseLeftovers · class · Config layer
What an installation left on the site when no installation is in progress any more (spec 107, FR-022b). A request cut off by the host, or a release older than this one that could not give an installation up, can leave its pieces behind with no record of the installation they were of. Nothing uses them, and the screen says so, by name, rather than “No installation is in progress” beside them: staging a release unpacked for an installation that is not there recovery_file the recovery plugin, asking for a key that is neither an installation’s nor the kept release’s: there is nothing it could put back previous_unknown folders in previous/ with no journal saying what they are: there is no going back to them They go when the administrator says so, not when the screen opens: one of them is a must-use plugin, which the administrator is told of before it is removed.
Public API
Section titled “Public API”__construct(ReleaseStore $store, ReleaseStaging $staging, ReleaseJournal $journal, ReleaseRecoveryPlugin $recovery)
Section titled “__construct(ReleaseStore $store, ReleaseStaging $staging, ReleaseJournal $journal, ReleaseRecoveryPlugin $recovery)”found(): array
Section titled “found(): array”What is left, by what it is and where it is on the server. None while an installation is in progress: then all of it is that installation’s.
remove(): array
Section titled “remove(): array”Remove what is left. What a folder holds is set aside by one rename, and deleted a few seconds at a time when the screen next opens, as a kept release is (FR-024b).