|
|
1 miesiąc temu | |
|---|---|---|
| .. | ||
| backups | 1 miesiąc temu | |
| .htaccess | 1 miesiąc temu | |
| README.md | 1 miesiąc temu | |
| config.sample.php | 1 miesiąc temu | |
| index.php | 1 miesiąc temu | |
| manage.php | 1 miesiąc temu | |
| upload.php | 1 miesiąc temu | |
This folder can be deployed as a central backup server for distributed PSA orderform instances.
config.sample.php to config.php.BACKUP_SERVER_PASSWORD.backups/ directory is writable by PHP.index.php or manage.php and log in with the configured password.The upload endpoint is upload.php. It intentionally does not require authentication, but every upload must include an instance identifier that was added in the management UI.
Configure a distributed instance with a managed backup target:
define('BACKUP_REMOTE_TARGETS', [
[
'name' => 'Managed Backup Server',
'type' => 'managed',
'url' => 'https://backup.example.org/upload.php',
'instance' => 'stadt-freising-prod',
],
]);
url must point directly to upload.php. instance may contain letters, numbers, dots, underscores, and dashes.
The server retains the latest backups per instance. The default is 30.
Retention can be changed in config.php with BACKUP_SERVER_RETENTION and in the management UI. The UI value is stored in backups/settings.json and takes precedence after it has been saved once.
Retention is applied after every successful upload and after retention changes in the management UI.
Backups are stored under:
backups/<instance>/backup-YYYYmmdd-HHMMSS.zip
Metadata is stored in:
backups/index.json
Allowed instances and UI retention settings are stored in:
backups/settings.json
With the included .htaccess, ZIP and JSON files are not directly readable through Apache. Downloads should use the authenticated management UI.