|
|
il y a 1 mois | |
|---|---|---|
| .. | ||
| packages | il y a 1 mois | |
| .htaccess | il y a 1 mois | |
| README.md | il y a 1 mois | |
| config.sample.php | il y a 1 mois | |
| index.php | il y a 1 mois | |
| manage.php | il y a 1 mois | |
| manifest.json | il y a 1 mois | |
| manifest.php | il y a 1 mois | |
| package.php | il y a 1 mois | |
This folder can be deployed as the central update server.
Release ZIPs can be managed through manage.php:
config.sample.php to config.php.UPDATE_SERVER_PASSWORD.index.php or manage.php, log in with the configured password, and upload a ZIP with a vX.Y.Z version.The management UI stores the ZIP under packages/, calculates SHA-256 and size, and updates manifest.json.
Manual release management is also possible:
packages/, for example packages/psa-orderform-v1.3.3.zip.manifest.json and set latest to the version clients should install.Example release entry:
{
"latest": "v1.3.3",
"releases": {
"v1.3.3": {
"version": "v1.3.3",
"package": "packages/psa-orderform-v1.3.3.zip",
"sha256": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
"size": 123456,
"published_at": "2026-06-23T00:00:00+00:00"
}
}
}
Clients should use manifest.php, not manifest.json, as their UPDATE_MANIFEST_URL.