|
|
пре 1 месец | |
|---|---|---|
| .. | ||
| includes | пре 1 месец | |
| packages | пре 1 месец | |
| .htaccess | пре 1 месец | |
| README.md | пре 1 месец | |
| config.sample.php | пре 1 месец | |
| index.php | пре 1 месец | |
| manage.php | пре 1 месец | |
| manifest.json | пре 1 месец | |
| manifest.php | пре 1 месец | |
| package.php | пре 1 месец | |
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.UPDATE_SERVER_PACKAGE_PREFIX to the project/package name.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/my-app-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/my-app-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.
The server code is intentionally project-agnostic. To reuse it in another PHP project, copy this folder, keep includes/update-server.php with the public PHP files, and adjust only config.php.