Skip to main content

Your environment

An environment is one company's isolated place to run its applications. It has its own addresses, its own database, its own files and its own backups. Open it from Hosting → Environments.

Overview​

The Overview is the compact answer to "is everything as it should be?":

  • the environment's current state, and whether a change is still being applied;
  • the applications it contains, and whether each is serving;
  • the browser tools for the environment;
  • a link to technical detail under Troubleshooting.

When a change is still being applied​

Changes are applied in the background. A change is not lost if it takes a moment:

  • Applying — the change is queued or in progress. Keep working; the page updates.
  • Failed — the change could not be applied. The failure is recorded, and the environment may have applied only part of the change. Check its current state and contact support if service is affected.
  • Applied — the recorded desired state and what is running agree.

If a change fails, use Retry and read the message it reports. A retry re-applies the same recorded intent, so you do not have to enter anything again.

If two people change the same environment at once, one of them is told the change is stale rather than overwriting the other. Reload and make the change again against the current state.

Tools​

The Overview opens the environment's browser tools:

ToolWhat it is for
FilesBrowse and edit the environment's application files
DatabaseRun SQL against an application's database (phpMyAdmin)
TerminalA shell inside the environment

All three open already signed in with your Hosting account, in their own browser tab. Choosing the same tool again focuses the tab you already have instead of opening a second one, so you do not lose work in it. If your browser blocks the new tab, allow pop-ups for Hosting and try again.

The tools reach the whole environment. A browser tool that can run SQL or edit files is as powerful as the credentials it uses, so treat access to it as administrator access.

Troubleshooting​

Troubleshooting shows the technical detail behind the state: the environment's identifier, the generation that has been applied, each workload's instance count and allocation, storage claims and databases. It is there for when you are working something out with us, and it changes nothing.

Settings​

Settings owns the numbers behind the environment and the way out of it:

  • the purchase — the CPU, memory and storage totals the environment has bought;
  • the allocation — how those totals are divided between the database, the applications and the tools;
  • a concise entry to cancelling hosting, with its current status.

You can change the allocation inside the purchase at any time. An allocation above the purchase is refused as a field error rather than silently reduced. A change that applies immediately is marked as such; a change that needs a restart says so before you submit.

See Cancelling hosting for the leaving path.

Next​

  • Open a site or an administrator login: Applications.
  • Move the allocation between workloads: Settings.