Staging Manager
Deutsch Demo shop View in the StoreStore

Manual The run window.

Every run opens the run window: rebuild, refresh data, closing check, comparison and teardown. It shows beforehand what the run does, meanwhile every step and afterwards how it ended. The preflight has a window of its own; every build runs it as its first step.

Before the start

Confirming what the run does.

Before a build and before a refresh the window shows what the run does and with what. Extensions, admin users and a few options can be switched here for this run only; the saved settings stay. The password page and a new password, however, it saves.

The tabs

Progress, check results, protocol, settings.

Progress
Step by step what the run did, each step with progress and status.
Check results
The results of preflight and closing check, each point "Fine", "Hint" or "Error".
Protocol
Every line the run wrote; how detailed it is, is set by "Detail of the run protocol".
Settings
What the run worked with, recorded at the start, even if the staging environment changed since.
Close, continue, cancel

A run does not hang on the window.

  • You may close the window. The background then carries the run on if "Carry runs in the background" is on and the live shop runs scheduled tasks; otherwise it waits until you open it again with "Continue run".
  • Cancelling ends an open run for good after the current slice; what it already did stays.
  • A failed build sets the staging environment to "Failed". The window says in which step it failed and how to fix it; a new run that succeeds makes it ready again.
  • Status of a run: Waiting, Waiting for a free slot, Running, Finished, Failed, Cancellation requested or Cancelled.
Preflight

A verdict, then the areas.

At the top it says whether the build can go ahead, such as "Ready for the first build", below one sentence per area: protection of the live shop, folder and web server, database, privacy, PHP and background, services and tasks.

  • Each point says what it means and what you can do; a click leads to the tab where you fix it. Then "Check again".
  • It lists separately what lies in the live shop folder but not in the list; that does not stop the build.
Closing check

What is checked at the end of every build.

  • The staging flag is set.
  • Every address answers, and the staging banner is visible.
  • robots.txt confirms the general crawl exclusion.
  • The administration answers, and media files are served.
  • The plugin in the staging environment answers, and the services are as set.

What it is all for

The manual says where something sits in the administration. Why it is like that and what it brings day to day is explained on the topic pages.

More on this:Setting upHosting and server

More chapters