@@PRODUCT@@

Your customers' applications

As a reseller you see every application of your accounts on one page: Accounts → Applications. You only see your own accounts and your customers' — never another reseller's. A server administrator sees the applications on their own servers

Written for: Reseller, Administrator

As a reseller you see every application of your accounts on one page: Accounts → Applications. You only see your own accounts and your customers' — never another reseller's. A server administrator sees the applications on their own servers and the administrator sees everything; they also pick the realm at the top.

What each application shows

  • Application — the website (and folder) it is on.
  • Account — which account it belongs to. Click a row to open that account's Applications page.
  • Version — the version the server last measured.
  • Status — Up to date, Update (with the new version), Vulnerable (the update closes a known hole) or Failed (the last update did not work or was rolled back). Not measured yet means the server has not looked at the application yet.
  • Policy — what the application may update by itself: Nothing by itself, Security only or All updates.
  • Last update — when, and from which version to which.

Filter on account, application, status and policy. The status Vulnerable shows you straight away what comes first.

How fresh it is. The page does not ask the servers each time you open it: the panel reads every server in the background and the page shows what it read last, with the age under the notices ("read 3 minutes ago"). After Update now the servers concerned are read again shortly.

A server is not answering. If a server did not answer its last reading, a notice at the top names the accounts concerned; their applications are missing for now, and the rest are there as usual. The page never waits for such a server. Try again later.

The account filter lists the accounts that have an application.

Several at once

Tick applications — from different accounts too — and choose:

  • Update now — each application gets a restore point first, is updated and checked, and goes back by itself if the check fails.
  • Set policy — the same update policy for all of them.
  • Make restore point — a copy of each application's files and database. It counts against the account's disk space, and each application can have three.

Under Result per application you see what happens per account, and then per application Done, Skipped (with the reason) or Failed. If something goes wrong with one application, the others carry on.

Backups

Your customers' backups have a page of their own: To your customers' backups at the top takes you there, and To your customers' applications on that page brings you back.

On the server itself

A reseller has no terminal on the server; the administrator sees the same list of one or more accounts there:

corectl app list --accounts web1,web2
corectl app bulk snapshot --account web1 --instances wordpress:example.com

Presets for your customers

Below the list is Presets: ready-made sets your customers install from. A preset is an application, a version choice (latest, or series:4.5 for the newest of a series), the plugins or theme that come with it right away (WordPress: wordpress.org slugs; Joomla: https package addresses) and the update policy the installation starts with. Your customers see your presets at the top of the install wizard, above the catalogue; the platform's own presets are there too. A preset of yours is visible in your own realm only, never at another reseller's.

An administrator makes presets for the whole platform, or for one realm.

See also

  • Maintaining applications
  • Restore points of applications
  • Your customers' backups