Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>

Signed-off-by: Julius Härtl <jus@bitgrid.net>

Signed-off-by: Morris Jobke <hey@morrisjobke.de>

Just to avoid users from trying this with a to new (untested) php version

* Moved the check logic to 1 place
* All directly callable scripts just require this on top
* exit hard (-1) so we know scripts won't continue
* Return status 500 so no sync clients will try fancy stuff

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

Signed-off-by: Morris Jobke <hey@morrisjobke.de>

Signed-off-by: Lukas Reschke <lukas@statuscode.ch>

During upgrades, before the DB migration is complete, the system is not
usable, but there's no way for monitoring systems to detect this.
Add the 'needupgrade' field to the status json so monitoring systems can
detect this.

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

Signed-off-by: Joas Schilling <coding@schilljs.com>

identifyer -> identifier

removed variable

* fix XMLHttpRequest - send after callback is registered
* check for correct type of value - it's a boolean
* return correct content-type in status.php

This reverts commit 6a1a4880.

* files_encryption
* files_versions
* files_trashbin
* tests
* status.php
* core
* server container

Using status.php for this.
I modified status.php to also show, whether we're in maintenance.

Checks every 20 seconds if maintenance is over, if yes: reload.

Fixes https://github.com/owncloud/core/issues/8342

Added option to use the status.php with console.php via CLI

This is for all LowerCaseConstant warnings

respect coding style

Show the different editions to the user. Used in the status call, on the personal settings page and in the updater to update to the next available version from the same edition.