Haɓaka na cikin gida tare da zinnector dev

zinnector dev yana gudanar da WordPress na gaske a kan na'urarku kanku, yana bada manhajojin plugin da jigogin (themes) da ke cikin aikinku, tare da nau'in PHP da kuka zaba. Wannan makala tana bayanin mahallan gudanarwa (runtimes) guda biyu da zai iya amfani da su, yadda ake zabar nau'o'i, abin da ake badawa daga ina, da kuma inda mahallin gudanarwar yake a kan diski — ta yadda abin da kuka gwada a kan na'urarku zai zama ainihin abin da kuka tura.

Mahallan gudanarwa guda biyu, da dalilin da ya sa dukansu na gaske ne

Playground shine zabin asali. WordPress Playground yana mayar da PHP zuwa WebAssembly sannan ya gudanar da shi a cikin Node, saboda haka kwamfutar tafi-da-gidanka da ba a dora komai a kanta ba sai Node tana iya tayar da WordPress a cikin dakiku kadan. Kowane PHP daga 5.2 zuwa 8.5 yana nan. Yana dauke da karamin rukunin kari na PHP (intl, redis, memcached kamar yadda aka auna a tsarin da ake amfani da shi a yanzu), wanda ya isa ga mafi yawan ayyukan plugin da jigo.

Docker yana gudanar da kwantenonin asali na php-fpm da MariaDB. Yana da dan nauyi, yana bukatar daemon na Docker da kusan 1.2 GB na hotunan manhaja (images), kuma yana goyon bayan PHP 7.4 zuwa 8.5 — amma yana gudanar da ainihin PHP na asali tare da cikakken rukunin kari, gami da imagick da gd. Shi ne ainihin amsar da ta dace lokacin da abin da kuke bukatar gwadawa kari ne wanda tsarin WebAssembly ba ya dauke da shi.

zinnector dev                       # playground
zinnector dev --runtime docker      # native PHP + MariaDB

Ba a taba komawa Docker a asirce ba. Mahadin manhaja da yake tunanin yana kan WebAssembly amma a zahiri yana kan Docker, an ba shi amsar da ba daidai ba daga kayan aikin da ke kokarin bayar da taimako, don haka dole ne a neme shi da suna kai tsaye.

Zabar nau'o'in PHP da WordPress

zinnector dev --php 8.1 --wp 6.7    # develop against a specific pair
zinnector dev --port 9401           # when 9400 is taken
zinnector dev --no-login            # do not sign in to wp-admin automatically
zinnector dev --verbose             # show the runtime's own output

Zabin asali yana fitowa ne daga zinnector.json da ke cikin aikin — php, wordpress, runtime da port — wanda zinnector new yake rubutawa kuma wanda ya kamata ku adana (commit), domin kowa a kan aikin ya gudanar da nau'o'i iri daya. Tuta (flag) a layin umarni tana cin nasara a kan fayil din don wancan gudanarwar.

Nau'in da kuka bayyana da kuma nau'in da yake gudu abubuwa ne daban-daban. zinnector dev --once yana tayar da mahallin gudanarwar, ya nuna abin da yake bayarwa a zahiri — nau'in PHP, nau'in WordPress, karin da aka loda — sannan ya tsaya. zinnector check --probe yana amfani da irin wannan awo lokacin da yake kwatanta aikinku da gurbin karbar baki (hosting slot).

Abin da ake bayarwa daga aikinku

Mahallin gudanarwar yana dora kundayen wp-content/plugins, wp-content/themes da wp-content/mu-plugins na aikinku kai tsaye, saboda haka fayil din da kuka ajiye yana aiki nan take idan an sake lodawa. Kundayen da suke akwai amma ba su dauke da ainihin abun ciki da gangan ba a dora su ba: shafin themes/ da babu komai a ciki da aka dora a kan ainihin jigogin mahallin gudanarwar zai bar WordPress ba tare da wani jigo ko daya ba, wanda hakan kuskuren 500 ne maras komai maimakon shafinku. Wannan shine dalilin da ya sa tsarin ginin yake ajiye kundayen da babu komai a ciki tare da .gitkeep da kuma dalilin da ya sa ba sa rufe komai har sai kun sanya jigo a cikinsu.

Inda mahallin gudanarwar yake

Ana sauke mahallin gudanarwa na WordPress ne a karon farko da aka yi amfani da shi maimakon a turo shi tare da CLI — kunshin da ke dauke da kowane ginin PHP kusan 570 MB ne, kuma mahadin manhaja da yake lissafa shafuka kawai bai kamata ya biya wannan nauyi ba. Ana ajiye shi a ma'ajiyar sirri ta Zinnector®, ~/.cache/zinnector/runtimes/playground/<version> (ko kuma duk inda ZINNECTOR_CACHE_DIR yake nuna), ba a taba ajiye shi a cikin aikinku ba, don haka ba zai iya shiga cikin ma'adanar aikinku (repository) ko cikin bishiyar da zinnector push yake aunawa ba. npm naku ne yake yin saukarwar, wanda ake gudanarwa a matsayin node npm-cli.js — ba a taba yi ta hanyar shell ba.

Nau'in mahallin gudanarwar yana daure ne da nau'in CLI, don haka masu hada manhaja guda biyu a kan aiki daya suna gudanar da gine-ginen PHP iri daya. zinnector dev --reset-runtime yana goge mahallin gudanarwar da aka girka sannan ya sake girka shi, wanda shine mafita ga mahallin gudanarwar da ya girku amma ya ki tashi.

A kan Node 26 ko mafi sabuntawa

CLI da kanta tana aiki a kan kowane Node daga 24 zuwa sama. Sai dai kuma, asalin manhajar mahallin gudanarwar tana fitar da tsararrun binary ne kawai don Node 24 da 25 (kamar yadda yake a watan Satumba 2026). Maimakon a hada wani abu (compile) — wanda a Windows ke nufin girka Visual Studio — Zinnector® yana samo Node 24 don mahallin gudanarwar shi kadai, wanda girmansa ya kai kusan 30 MB, an tabbatar da shi ta hanyar lambobin tabbatarwa (checksums) da nodejs.org ke wallafawa, zuwa cikin wannan ma'ajiyar. Sanarwar girka manhaja tana bayyana hakan lokacin da ya dace. Babu wani abu da zai canza game da ainihin Node naku.

Masu alaka

• Fara aiki · Turawa · Bayanin umarni · Magance matsala