PUT /v1/sites/{siteId}/php-version

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin hosting.php.manage; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/php-version \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "version": <string> }'

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

Sets the site's desired PHP version and returns 202 Accepted. The target must be a version currently offered for the site's product line (or the site's own current version); anything else is a 422. A retired version an existing site already runs is kept — this call never forces a migration. Requires hosting.php.manage. The machine serving the site is told before the row is written, on both lines: one ack-checked vendor call on the resold range, and one idempotent cloudlinux-selector set --current-version= on our own fleet. A version the machine refuses is a 422 and the row is left alone, so the platform never claims a runtime the box is not running. 202 therefore under-promises rather than over-promises. A site with no hosting vendor and no placed worker has nothing serving it yet: the desired version is recorded and provisioning applies it. The site's PHP extensions move with it. The PHP selector keeps extensions per version, so once the machine confirms the switch, the site's composed extension set is pushed for the new version: the platform floor, the customer's own toggles, and whatever its one-click application needs. Without this, a site landed on the new version's default set; a Drupal site answered 500 on every page with no dom (D24906). If that push fails, the switch still stands, and the hourly PHP-settings converge pushes the set on its next pass. A machine that cannot be reached at all — its account does not exist yet, SSH is down, the vendor is unavailable — is a 503, not a 422 and not a 500: the request was valid and a retry can succeed. The stored version is left exactly as it was, so a 503 here means nothing changed anywhere.

Sigogi

Jikin buƙata

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 422 · 429 · 503