Ci gaban gida tare da zinnector dev

zinnector dev yana gudanar da ingantaccen WordPress a kan kwamfutarka ta kanka, yana samar da ma'aikata (plugins) da jigogi (themes) a cikin aikinku, tare da sigar PHP da ka zaba. Wannan makalar tana bayyana nau'ikan muhallan gudanarwa guda biyu da za a iya amfani da su, yadda za a zabi sigogi, abin da ake samarwa daga ina, da kuma inda muhallin gudanarwar yake a kan faifai (disk) — domin abin da ka gwada a kwamfutarka shi ne abin da za ka tura.

Muhallan gudanarwa guda biyu, da dalilin da ya sa dukansu ingantattu ne

Playground shi ne tsohuwar zabin (default). WordPress Playground yana fassara PHP zuwa WebAssembly sannan yana gudanar da shi a cikin Node, don haka kwamfutar tafi-da-gidanka da ba a shigar da komai a cikinta ba sai Node tana tayar da WordPress a cikin dakiku kadan. Kowane PHP daga 5.2 zuwa 8.5 yana samuwa. Yana dauke da karamin rukunin karin fensho na PHP (intl, redis, memcached kamar yadda aka auna a sigar yanzu), wanda ya wadatar ga yawancin ayyukan plugin da theme.

Docker yana gudanar da ainihin akwatunan php-fpm da MariaDB. Yana da hankali aiki, yana buqatar Docker daemon da misalin 1.2 GB na hotuna (images), kuma yana goyon bayan PHP 7.4 zuwa 8.5 — amma yana gudanar da ainihin PHP tare da cikakken rukunin karin fensho, har da imagick da gd. Shi ne ingantaccen amsar lokacin da abin da kake buqatar gwadawa shine karin fenshon da ginin WebAssembly ba ya dauke da shi.

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

Taba ba a komawa zuwa Docker a boye ba tare da sanarwa ba. Injiniyan da ya dauka yana kan WebAssembly amma a zahiri yana kan Docker an ba shi amsar da ba daidai ba ta hanyar kayan aiki da ke kokarin taimakawa, don haka dole ne a buqace shi ta hanyar sunansa.

Zabar sigogin 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

Tsoffin zabuuka suna fitowa ne daga zinnector.json a cikin aikin — php, wordpress, runtime da port — wanda zinnector new yake rubutawa kuma wanda ya kamata ku ajiye (commit), domin kowa a cikin aikin ya gudanar da sigogi iri daya. Tutar da ke kan layin umarni tana yin nasara a kan fayil din don wannan gudanarwar.

Sigar da ka sanar da sigar da ke gudanarwa abubuwa ne guda biyu mabanbanta. zinnector dev --once yana tayar da muhallin gudanarwa, ya buga abin da yake rahoto a zahiri — sigar PHP, sigar WordPress, karin fensho da aka gano — sannan ya tsaya. zinnector check --probe yana amfani da gwaji iri daya lokacin da yake kwatanta aikinka da wajen karbar bakuncin yanar gizo (hosting slot).

Abin da ake samarwa daga aikinku

Muhallin gudanarwar yana haɗa kundayen aikinku na wp-content/plugins, wp-content/themes da wp-content/mu-plugins kai tsaye, don haka fayil ɗin da ka adana yana aiki nan take a sake lodawa na gaba. Kundayen da ke akwai amma ba su ɗauke da ainihin abun ciki da gangan ba za a haɗa su ba: wani themes/ mai wofi da aka haɗa a kan muhallin gudanarwar zai bar WordPress ba tare da wani theme ba kwata-kwata, wanda shine 500 mai wofi maimakon shafinka. Shi ya sa tsarin ginin yake riƙe empty kundayen da .gitkeep da kuma dalilin da ya sa ba sa rufe komai har sai ka sa theme a cikinsu.

Inda muhallin gudanarwar yake

Ana sauke muhallin gudanarwa na WordPress a amfani na farko maimakon a turo shi tare da CLI — kunshin da ke ɗauke da kowane ginin PHP yana kusan MB 570, kuma injiniyan da kawai yake jera shafuka bai kamata ya biya shi ba. Ana ajiye shi a cikin ma'ajiyar sirri ta Zinnector®, ~/.cache/zinnector/runtimes/playground/<version> (ko duk inda ZINNECTOR_CACHE_DIR ke nuna), ba a cikin aikinku ba, don haka ba zai iya ƙarewa a cikin ma'ajiyarku ko a cikin bishiyar da zinnector push ke aunawa ba. Sauke abun ana yin sa ne ta hanyar npm na kanku, wanda aka gudanar azaman node npm-cli.js — ba ta hanyar shell ba.

Sigar muhallin gudanarwa an kulle ta zuwa sigar CLI, don haka injiniyoyi guda biyu a kan aiki ɗaya suna gudanar da ginannun PHP iri ɗaya. zinnector dev --reset-runtime yana yar da muhallin gudanarwa da aka shigar sannan ya sake shigar da shi, wanda shi ne mafita ga muhallin gudanarwa da aka shigar amma ba zai tashi ba.

A kan Node 26 ko sababbi

CLI kanta tana gudanarwa akan kowane Node daga 24 zuwa sama. Sakamakon ma'aunin muhallin gudanarwa na native module, duk da haka, yana tura ginannun binaries kawai don Node 24 da 25 (daga Satumba 2026). Maimakon haɗa komai — wanda a kan Windows ke nufin shigar da Visual Studio — Zinnector® yana ɗauko Node 24 don muhallin gudanarwa kawai, kusan MB 30, wanda aka tabbatar da shi game da checksums nodejs.org ke wallafawa, zuwa ma'ajiya iri ɗaya. Abin da shigarwar ke faɗa lokacin da yake aiki yana bayyana hakan. Babu abin da zai canza game da Node ɗinku.

Masu alaƙa

• Fara amfani · Turawa · Manazarta umarni · Kyakkyawan warware matsala