Hifadhidata ya maarifa

Mwongozo wa amri za Zinnector®

Kila amri ya Zinnector® sawasawa jinsi zinnector --help inavyoorodhesha — hoja, bendera na chaguo-msingi, mfano unaoweza kutekelezwa na kile inachochapisha — imezalishwa kutoka kwa CLI yenyewe ili isiweze kutofautiana na toleo ulilosakinisha.

Kila amri ambayo Zinnector® 0.1.6 inaelewa — 43 kwa jumla, sawasawa na jinsi zinnector --help inavyoorodhesha — pamoja na chaguo zake, mfano unaoweza kuendeshwa, na kile unachopaswa kuona. Ukurasa huu unazalishwa kutoka kwa CLI yenyewe, kwa hivyo hauwezi kutofautiana na zana uliyosakinisha; ikiwa amri iliyopo hapa inakosekana kwenye mashine yako, endesha npm install -g zinnector@latest.

Kabla ya kuanza

Isakinishe kwa npm install -g zinnector kwenye Node 24 au mpya zaidi, kisha uhakiki usakinishaji kwa zinnector --version na zinnector --help. Mwongozo wa kuanza unaeleza hatua za dakika tano za kwanza; ukurasa huu ni rejeleo unalorudia.

Kila amri inachukua -h, --help. Chaguo hizi za jumla huwekwa kabla ya jina la amri:

option	what it does
`-V, --version`	chapisha toleo
`--profile <name>`	tumia wasifu wa stakabadhi wenye jina

Amri

`zinnector new`

Unda muundo wa mradi wa WordPress unaoweza kuuendesha mara moja.

zinnector new [options] [name]

hoja	inahitajika	ni nini
`name`	hapana	saraka ya kuunda mradi ndani yake, na jina la mradi — inahitajika isipokuwa --here

chaguo	inachofanya	chaguomsingi
`-t, --template <kind>`	mojawapo ya: site, plugin, theme	`"site"`
`--php <version>`	toleo la PHP la kutengenezea programu	`"8.3"`
`--wp <version>`	toleo la WordPress kwa ajili ya mazingira ya ndani ya utekelezaji	`"latest"`
`--runtime <name>`	playground au docker	`"playground"`
`--here`	jenga muundo katika saraka ya sasa badala ya mpya

Mfano

zinnector new my-site

Unachokiona — kimenaswa — 0.1.2 kwenye Linux

Created my-site  ·  site
──────────────────────────

  + .gitignore
  + README.md
  + wp-content/mu-plugins/000-zinnector-dev.php
  + wp-content/plugins/.gitkeep
  + wp-content/themes/.gitkeep
  + zinnector.json

  php        8.3
  wordpress  latest
  runtime    playground

→ run it:
    cd my-site
    zinnector dev

→ then, when you have a hosting slot:
    zinnector link     # point it at a site
    zinnector check    # pre-flight before you push
    zinnector push

`zinnector dev`

Endesha mradi huu ndani ya kifaa — Docker haihitajiki.

zinnector dev [options]

chaguo	kazi yake	chaguo-msingi
`--php <version>`	toleo la PHP la kuendesha (5.2–8.5 kwenye playground, 7.4–8.5 kwenye docker)
`--wp <version>`	toleo la WordPress
`-p, --port <port>`	lango la kutoa huduma
`--runtime <name>`	playground (chaguo-msingi) au docker
`--login`	ingia kiotomatiki kama msimamizi	`true`
`--no-login`	usiingie kiotomatiki
`--once`	washa, ripoti kile kinachoendeshwa, kisha simamisha
`--yes`	sakinisha runtime ya ndani bila kuuliza
`--reset-runtime`	futa runtime iliyosakinishwa na uisakinishe tena
`-v, --verbose`	onyesha matokeo ya runtime yenyewe

Mfano

cd my-site
zinnector dev

Unachokiona — kimenaswa — 0.1.2. Uendeshaji wa kwanza huuliza mara moja ili kupakua mazingira ya utekelezaji ya WordPress (~570 MB); pitisha --yes ili kuruka swali

my-site  ·  WordPress Playground (WASM, no Docker)
───────────────────────────────────────────────────

  serving    a WordPress project
  from       /home/you/my-site
  php        8.3
  wordpress  latest

✔ running at http://127.0.0.1:9400
  admin: http://127.0.0.1:9400/wp-admin  (already signed in)

  Ctrl-C to stop

`zinnector login`

Ingia — ukitumia akaunti yako mwenyewe kwenye kivinjari, au ukitumia ufunguo wa API.

zinnector login [options]

chaguo	inachofanya	chaguo-msingi
`--profile <name>`	hifadhi chini ya wasifu uliotajwa jina (chaguo-msingi: default)
`--api <url>`	URL ya msingi ya API	`"https://api.zinndigital.com"`
`--api-key`	bandika ufunguo wa API wa shirika badala ya kuingia kama wewe mwenyewe
`--issuer <url>`	huduma ya kuingia	`"https://auth.zinndigital.com/realms/zinn"`
`--no-browser`	chapisha kiungo cha kuingia bila kujaribu kufungua kivinjari

Mfano

zinnector login

Unachokiona — ufunguo huandikwa kwenye kiashiria, si kamwe kwenye mstari wa amri. Kwenye CI, upitishe kwa bomba: echo "$ZINN_API_KEY" | zinnector login --profile ci

Sign in to Zinn Digital®  ·  https://api.zinndigital.com
────────────────────────────────────────────────────

  API key: ••••••••••••••••••••••••••••

✔ signed in as you@example.com (Acme Ltd) — profile “default”
→ next: zinnector sites

`zinnector logout`

Sahau kuingia kulikohifadhiwa.

zinnector logout [options]

chaguo	inachofanya	chaguomsingi
`--profile <name>`	wasifu upi wa kusahau (chaguomsingi: default)

Mfano

zinnector logout

Unachokiona

✔ signed out of profile “default”

`zinnector whoami`

Onyesha ni nani ambaye CLI hii imeingia kama yeye, na inachoweza kufikia.

zinnector whoami [options]

| chaguo | kile inachofanya | chaguo-msingi |\n|---|---|---|\n| --profile <name> | tumia wasifu wenye jina | |\n| --scopes | orodhesha ruhusa ambazo ufunguo wa API unabeba | |\n| --json | matokeo yanayosomwa na mashine | |\n\nMfano

zinnector whoami --scopes

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Signed in  ·  https://api.zinndigital.com
──────────────────────────────────────────
account        you@example.com
as             a person, signed in through the browser
organisations  8 — listed below
mode           live
credential     profile “default”

  · Example Org  owner · 01a00000-0000-7000-8000-000000000000
  · Example Org· 01a00001-0000-7000-8000-000000000001
  · Example Org· 01a00002-0000-7000-8000-000000000002
  · Example Org· 01a00003-0000-7000-8000-000000000003
  · Example Org· 01a00004-0000-7000-8000-000000000004
  · Example Org· 01a00005-0000-7000-8000-000000000005
  · Example Org· 01a00006-0000-7000-8000-000000000006
  · Example Org· 01a00007-0000-7000-8000-000000000007

  scopes belong to API keys — a signed-in person acts with their ROLE in each organisation (shown above).

`zinnector sites`

Orodhesha tovuti ambazo ufunguo huu unaweza kuona.

zinnector sites [options]

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomwa na mashine
`--status <status>`	tovuti pekee zilizo katika hali hii

Mfano

zinnector sites

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Sites  ·  12
─────────────
domain          status  php      target  id
example-2.com   active  php —    fleet   01a00000-0000-7000-8000-000000000000
example-3.com   active  php —    fleet   01a00001-0000-7000-8000-000000000001
example-4.com   active  php —    fleet   01a00002-0000-7000-8000-000000000002
example-5.com   active  php 8.5  fleet   01a00003-0000-7000-8000-000000000003
example-6.com   active  php —    fleet   01a00004-0000-7000-8000-000000000004
example.com     active  php 8.4  fleet   01a00005-0000-7000-8000-000000000005
example-7.com   active  php —    fleet   01a00006-0000-7000-8000-000000000006
example-8.com   active  php 8.5  fleet   01a00007-0000-7000-8000-000000000007
example-9.com   active  php 8.5  fleet   01a00008-0000-7000-8000-000000000008
example-10.com  active  php 8.5  fleet   01a00009-0000-7000-8000-000000000009
example-11.com  active  php 8.5  fleet   01a00010-0000-7000-8000-000000000010
example-12.com  active  php 8.5  fleet   01a00011-0000-7000-8000-000000000011

`zinnector status`

Kila kitu ambacho jukwaa linajua kuhusu tovuti moja.

zinnector status [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector status example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


example.com  ·  01a00000-0000-7000-8000-000000000000
────────────────────────────────────────────────────────────────────────
status         active
product line   footprint_free
stack          wordpress
region         fsn1
deploy target  fleet
plan           PBN 10

● PHP
version        8.4
can switch to  8.5, 8.4, 8.3, 8.2, 8.1, 8.0, 7.4

● Quota
disk      188 MB used of 500.0 GB
files     6,313 of 2,000,000
database  1 MB

● Deploy
status         building
target         fleet
repository     —
commit         —
live url       —
last deployed  2026-09-14T01:29:26.991511Z

● WordPress
version     7.1
up to date  yes
multisite   no

`zinnector share`

Mpe mtu mmoja ufikiaji wa tovuti MOJA — msanidi programu, mbunifu, mteja.

zinnector share [options] <site> <email>

hoja	inahitajika	kile ilicho
`site`	ndiyo	tovuti ya kushiriki — id, kikoa kikuu au jina
`email`	ndiyo	nani wa kumpa ufikiaji — wanatumiwa mwaliko kwa barua pepe ikiwa bado hawana akaunti

chaguo	kile inachofanya	chaguomsingi
`--role <role>`	kile wanachoweza kufanya: viewer, editor, manager
`--reason <text>`	kwa nini wanaihitaji — huwekwa pamoja na idhini kwa ajili ya ukaguzi
`--until <date>`	wakati ufikiaji unapoisha wenyewe (YYYY-MM-DD); acha kwa hadi-itakapofutwa
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector share example.com dev@agency.test --role editor --reason "rebuild the checkout"

Unachokiona — umbo kamili ambalo amri huchapisha, kutoka chanzo (W40-DEVTOOL iliongeza hivi baada ya faili hii kunaswa mara ya mwisho); vikoa vyako, vitambulisho na tarehe vitatofautiana

Shared example.com  ·  01a03f39-730a-7dc4-84b0-5d4f7582dd04
────────────────────────────────────────────────────────────

✔ invited dev@agency.test as editor
  They have no account yet, so an invitation has been emailed. Until they
  sign in and accept it they can see nothing; the moment they do, the site is theirs.

→ what they do next, on their own machine:
    npm i -g zinnector && zinnector login   # sign in as themselves
    zinnector clone example.com   # pull the files down

`zinnector collaborators`

Nani amepewa idhini ya kufikia tovuti, na kama amekubali.

zinnector collaborators [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector collaborators example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. umbo halisi ambalo amri huchapisha, kutoka chanzo (W40-DEVTOOL iliongeza hivi baada ya faili hii kunaswa mara ya mwisho); vikoa, vitambulisho na tarehe zako zitatofautiana


Access to example.com  ·  3
───────────────────────────────────────────────────────────
who              role    status   ends  why                                          grant
dev@agency.test  viewer  revoked  —     Example Org— revoked immediately after       01a00000-0000-7000-8000-000000000000
dev@agency.test  viewer  revoked  —     Example Org— revoked at the end of the walk  01a00001-0000-7000-8000-000000000001
dev@agency.test  editor  revoked  —     Example Org— revoked at the end of the walk  01a00002-0000-7000-8000-000000000002

`zinnector unshare`

Batilisha ufikiaji wa mtu kwenye tovuti — kwa barua pepe au kitambulisho cha ruzuku (grant id).

zinnector unshare [options] <site> <who>

hoja	inahitajika	ni nini
`site`	ndiyo	tovuti ya kurejesha ufikiaji wake — id, kikoa msingi au jina
`who`	ndiyo	mtu wa kuondolewa — barua pepe yake, au id ya ruzuku kutoka zinnector collaborators

chaguo	inachofanya	chaguomsingi
`--yes`	usiulize

Mfano

zinnector unshare example.com dev@agency.test --yes

Unachokiona — umbo kamili ambalo amri huchapisha, kutoka chanzo (W40-DEVTOOL iliongeza hivi baada ya faili hii kunaswa mara ya mwisho); vikoa vyako, vitambulisho na tarehe vitatofautiana

✔ withdrew the invitation to dev@agency.test

`zinnector invitations`

Mialiko inayokungoja, na ukubali mmoja.

zinnector invitations [options] [command]

Mfano

zinnector invitations

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. umbo kamili linalochapishwa na amri, kutoka kwa chanzo (W40-DEVTOOL iliongeza haya baada ya faili hii kunaswa mara ya mwisho); vikoa, vitambulisho na tarehe zako zitatofautiana; bila amri ndogo huendesha list


Invitations  ·  0
──────────────────

● nothing waiting for you

`zinnector invitations list`

Mialiko inayoelekezwa kwenye akaunti uliyotumia kuingia.

zinnector invitations list [options]

chaguo	kile inachofanya	chaguo-msingi
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector invitations list


Invitations  ·  0
──────────────────

● nothing waiting for you

`zinnector invitations accept`

Kubali mwaliko — tovuti inakuwa yako punde tu amri hii inapokamilika.

zinnector invitations accept [options] <id>

hoja	inahitajika	ni nini
`id`	ndiyo	id ya mwaliko kutoka kwa zinnector invitations — kiambishi awali cha kipekee kinatosha

Mfano

zinnector invitations accept 01a03f39-9c11-7b02-a7e0-2e4d0c5f1b77

Unachokiona — umbo kamili ambalo amri huchapisha, kutoka chanzo (W40-DEVTOOL iliongeza hivi baada ya faili hii kunaswa mara ya mwisho); vikoa vyako, vitambulisho na tarehe vitatofautiana

✔ you now have access to example.com

`zinnector link`

Elekeza mradi huu kwenye nafasi ya upangishaji (na uunganishe hazina yake).

zinnector link [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inachofanya	chaguo-msingi
`--repo <owner/name>`	unganisha ghala hili na tovuti kwenye jukwaa
`--provider <name>`	akaunti iliyounganishwa ya kutumia kusambaza: github_app, github au gitlab (chaguo-msingi: ile ambayo shirika lenu limeunganisha)
`--branch <name>`	tawi ambalo shughuli ya push inasambaza kutoka kwake
`--no-repo`	andika zinnector.json pekee; usiguse jukwaa

Mfano

zinnector link example.com --repo acme/example-site --branch main

Unachokiona

✔ this project deploys to example.com (01a03f39-730a-7dc4-84b0-5d4f7582dd04)
  written to zinnector.json — commit it so everyone deploys to the same slot
✔ the platform will deploy acme/example-site (main)
→ next: zinnector check

`zinnector pull`

Vuta faili za tovuti iliyopangishwa kwenye mradi huu kwa ajili ya uundaji wa ndani — na uendeshe tena ili kusawazisha upya.

zinnector pull [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa msingi au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inafanya nini	chaguo-msingi
`--via <seam>`	auto (chaguo-msingi), git, au backup	`"auto"`
`--fresh`	chukua nakala rudufu mpya badala ya kutumia ya hivi punde (inatumia nafasi ya on-demand)
`--max-age <hours>`	kubali nakala rudufu ya hivi punde ikiwa ni mpya zaidi kuliko hii	`"24"`
`--full`	folda kuu yote ya hati, ikiwa ni pamoja na WordPress msingi (chaguo-msingi: wp-content pekee)
`--no-uploads`	acha nyuma wp-content/uploads (midia)
`--no-database`	acha nyuma hifadhidata ya tovuti — chukua faili pekee
`--live-config`	pia andika wp-config.php — inashikilia kitambulisho cha hifadhidata ya LIVE
`--clean`	toa vitu vyote kwenye wp-content kabla ya kutoa, ili ufutaji kwenye tovuti uakisiwe
`--dry-run`	sema kile ambacho kingetokea na usimame
`--yes`	usiulize

Mfano

zinnector pull

Unachokiona

Pull example.com  ·  01a03f39-730a-7dc4-84b0-5d4f7582dd04
─────────────────────────────────────────────────────────────

● via git — the site syncs to its own repository and this is a clone of it
✔ fast-forwarded 3 commits 4f1c2a9b → 9d2e7c14

● not synced, and why
  ✖ database                     the local playground has its own; the site's is not copied
  ✖ offloaded media              objects in storage are not in the site's files
  ✖ anything outside the repository  only wp-content syncs

→ next: zinnector dev

`zinnector clone`

Tengeneza mradi wa ndani kutoka kwa tovuti iliyopangishwa: iga ghala lake au vuta faili zake.

zinnector clone [options] <site> [dir]

hoja	inahitajika	ni nini
`site`	ndiyo	tovuti inayopangishwa ya kunakili — kitambulisho (id), kikoa msingi au jina
`dir`	hapana	saraka ya kuunda — chaguomsingi ni kikoa msingi cha tovuti

chaguo	inachofanya	chaguomsingi
`--via <seam>`	auto (chaguomsingi), git, au backup	`"auto"`
`--fresh`	chukua nakala rudufu mpya badala ya kutumia ya hivi punde zaidi
`--full`	mzizi mzima wa hati, ikijumuisha kiini cha WordPress
`--no-uploads`	acha nyuma wp-content/uploads (midia)
`--no-database`	acha nyuma hifadhidata ya tovuti — chukua faili pekee
`--live-config`	pia andika wp-config.php — ina vitambulisho vya hifadhidata HALISI
`--yes`	usiombe uthibitisho

Mfano

zinnector clone client.example.com

Unachokiona

Clone client.example.com  ·  client.example.com
──────────────────────────────────────────────────────

✔ wrote client.example.com/zinnector.json (php 8.3, wordpress 6.7.1)
● via backup — the site does not sync to a repository
✔ downloaded 214 MB and extracted wp-content

● not synced, and why
  ✖ database                     the local playground has its own; the site's is not copied
  ✖ offloaded media              objects in storage are not in the site's files
  ✖ wp-config.php                holds the live database credentials (--live-config to write it)
  ✖ WordPress core               the runtime supplies the version the slot runs (--full to take it)

→ next: zinnector dev

→ run it:
    cd client.example.com
    zinnector dev

`zinnector sync`

Usawazishaji wa njia mbili kati ya faili za moja kwa moja za tovuti na hazina yake.

zinnector sync [options] [command]

Mfano

zinnector sync --help

Unachokiona — bila amri ndogo, zinnector sync <site> ni sync status

Usage: zinnector sync [options] [command]

two-way sync between a site's live files and its repository

  site → repository   zinnector sync run   commits the live files and pushes the branch
  repository → site   zinnector push       builds the branch and publishes it

`zinnector sync status`

Hali ya uoanishaji wa pande mbili, na utendaji wake wa mwisho.

zinnector sync status [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector sync status example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.4 dhidi ya tovuti ya majaribio mnamo 2026-09-12; kikoa na vitambulisho vimebadilishwa na maadili ya mfano

Two-way sync — example.com
──────────────────────────

repository   acme/example-site (main)
available    yes
sync         on
state        synced
last sync    2026-09-12T22:51:41.539832Z
note         Started from acme/example-site@main.

run        files       commit         when
synced     2 changed   da85d73cef5f   2026-09-12T22:52:10.117301Z

`zinnector sync on`

Washa ulandanishi wa njia mbili (haisukumi chochote yenyewe).

zinnector sync on [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inachofanya	chaguo-msingi
`--subdir <path>`	sawazisha saraka ndogo hii tu ya tovuti
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector sync on example.com

Unachokiona — kinahitaji hazina iliyounganishwa kwenye akaunti yako mwenyewe ya GitHub; hakisukumi chochote chenyewe

✔ two-way sync is on

Two-way sync — example.com
…
→ next: zinnector sync run

`zinnector sync off`

Zima usawazishaji wa pande mbili.

zinnector sync off [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inachofanya	chaguo-msingi
`--subdir <path>`	sawazisha saraka ndogo hii tu ya tovuti
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector sync off example.com

Unachokiona

✔ two-way sync is off

`zinnector sync run`

Kabidhi faili za moja kwa moja za tovuti kwenye hazina yake sasa.

zinnector sync run [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector sync run example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.4 dhidi ya tovuti ya majaribio mnamo 2026-09-12; kikoa na vitambulisho vimebadilishwa na maadili ya mfano. Uendeshaji ambao hazina imekwisha upita badala yake HUZUILIWA (HELD): hakuna kitu kinachotumwa au kuandikwa tena, amri huondoka kwa 1 na kutaja hatua inayofuata

✔ committed 2 changed files da85d73cef5f

Two-way sync — example.com
…
→ next: git pull in your clone

`zinnector sync resolve`

Futa usawazishaji uliosimamishwa kwa kuchagua upande unaoshinda.

zinnector sync resolve [options] [site]

| hoja | inahitajika | ni nini |\n|---|---|---|\n| site | hapana | kitambulisho cha tovuti, kikoa kikuu au jina — chaguomsingi ni tovuti iliyounganishwa katika zinnector.json |\n\n| chaguo | inachofanya | chaguomsingi |\n|---|---|---|\n| --keep <side> | site (weka tovuti juu yake) au repository (tupa mabadiliko ya tovuti ambayo hayajasawazishwa) | |\n| --yes | usiulize | |\n| --json | matokeo yanayosomwa na mashine | |\n\nMfano

zinnector sync resolve example.com --keep repository --yes

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.4 dhidi ya tovuti ya majaribio mnamo 2026-09-12; kikoa na vitambulisho vimebadilishwa na thamani za mfano. Bila --yes huuliza kwanza, na hukataa moja kwa moja wakati hakuna terminal ya kuulizia

✔ kept the repository

Two-way sync — example.com
…
state        synced

`zinnector check`

Linganisha mradi huu na nafasi unayokaribia kuipeleka.

zinnector check [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	kitambulisho cha tovuti, kikoa kikuu au jina — chaguomsingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inachofanya	chaguomsingi
`--probe`	anzisha mazingira ya ndani ya utekelezaji na UPIME php yake, badala ya kuamini zinnector.json
`--all`	onyesha ukaguzi uliopita pia
`--strict`	feli pia wakati kitu hakikuweza kukaguliwa
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector check

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa — uendeshaji ulipata kutolingana halisi (PHP 8.3 katika mradi dhidi ya 8.4 kwenye nafasi), ambalo ndilo kusudi zima la amri

→ reading the slot
  size excludes: .git

Pre-flight — example.com  ·  01a00000-0000-7000-8000-000000000000
────────────────────────────────────────────────────────────────────────

  local  php 8.4  3 files, 0.0 MB
  slot   php 8.4  target fleet
  local php is the version DECLARED in zinnector.json — run with --probe to measure it

  ? unknown   local php extensions could not be enumerated
      try zinnector dev --once

  ? unknown   wordpress versions could not be compared
      No WordPress version found in the working copy.
      try zinnector status

  7 passed  ·  2 could not be checked

`zinnector push`

Kagua mapema, sukuma ahadi zako, na usambaze.

zinnector push [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	kitambulisho cha tovuti, kikoa kikuu au jina — chaguomsingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguomsingi
`-f, --force`	sambaza hata wakati ukaguzi wa awali una matokeo
`--skip-checks`	usiendeshe ukaguzi wa awali hata kidogo
`--probe`	pima muda wa utekelezaji wa ndani wakati wa ukaguzi wa awali badala ya kuamini zinnector.json
`--no-wait`	anzisha usambazaji na uondoke bila kuufuatilia
`--no-git`	usiendeshe git push; sambaza chochote ambacho jukwaa tayari linacho
`--dry-run`	fanya kila kitu isipokuwa usambazaji

Mfano

zinnector push

Unachokiona

Deploy to example.com  ·  01a03f39-730a-7dc4-84b0-5d4f7582dd04
───────────────────────────────────────────────────────────────

✔ pre-flight: 8 passed  ·  0 to look at  ·  2 could not be checked
→ pushing main (4f1c2a9b add the contact form)
✔ pushed
● deploy 7c0e… started — watching
✔ deployed 4f1c2a9b in 48s

  status    success
  commit    4f1c2a9b
  url       https://example.com

`zinnector deploy`

Sambaza upya kile ambacho jukwaa tayari linacho, bila kusukuma.

zinnector deploy [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	kitambulisho cha tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inachofanya	chaguo-msingi
`--no-wait`	anzisha na utoke

Mfano

zinnector deploy example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Redeploy example.com  ·  01a00000-0000-7000-8000-000000000000
────────────────────────────────────────────────────────────────────────
→ starting the deploy
✔ deploy started

`zinnector deploys`

Historia ya upelekaji wa tovuti.

zinnector deploys [options] [site]

argument	required	what it is
`site`	hapana	kitambulisho cha tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

option	what it does	default
`--json`	tokeo linalosomeka na mashine
`-n, --limit <n>`	idadi ya kuonyesha	`"10"`

Mfano

zinnector deploys example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Deploys — example.com  ·  2
───────────────────────────────────────────────────────────
status  commit  branch  trigger  started                      message
live    —       —       manual   2026-09-14T09:06:39.685554Z  —
live    —       —       manual   2026-09-14T01:29:20.196957Z  —

`zinnector php`

Onyesha au badilisha toleo la PHP la tovuti.

zinnector php [options] [version]

hoja	inahitajika	ni nini
`version`	hapana	toleo la PHP la kubadilishia tovuti, mfano 8.4 — acha ili kuonyesha toleo la sasa

chaguo	linafanya nini	chaguomsingi
`-s, --site <site>`	id ya tovuti au kikoa
`--list`	orodhesha matoleo yanayotolewa na jukwaa
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector php 8.3 --site example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. bila toleo inaonyesha toleo la sasa; --list inaonyesha kile jukwaa linatoa kwa laini ya bidhaa ya tovuti hii


PHP — example.com
──────────────────────────────────────────────────────
version        8.4
can switch to  8.5, 8.4, 8.3, 8.2, 8.1, 8.0, 7.4

`zinnector quota`

Matumizi ya diski, faili na hifadhidata dhidi ya kile ambacho mpango unatoa.

zinnector quota [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector quota example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Quota — example.com
────────────────────────────────────────────────────────
disk used      188 MB
disk limit     500.0 GB
disk granted   500 GB  (per_site)
files used     6,313
file limit     2,000,000
database       1 MB

  “limit” is what is enforced today; “granted” is what the plan says.

`zinnector db`

Ukubwa wa hifadhidata, na viungo vya matumizi ya mara moja kuelekea phpMyAdmin na kidhibiti faili.

zinnector db [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector db example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. viungo vya phpMyAdmin na kidhibiti faili ni vya matumizi moja na muda wake unaisha; usivibandike popote


Database — example.com
───────────────────────────────────────────────────────────
size    1 MB
tables  14

  single-use links, valid for one visit:
  phpMyAdmin    https://pma.example.com/signon.php?t=<single-use>
  file manager  https://files.example.com/signon.php?t=<single-use>

`zinnector logs`

Fuatilia kumbukumbu za ufikiaji na hitilafu za tovuti papo hapo.

zinnector logs [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	kitambulisho cha tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

chaguo	inachofanya	chaguomsingi
`--access`	kumbukumbu ya ufikiaji pekee
`--error`	kumbukumbu ya hitilafu pekee
`--build`	badala yake kumbukumbu ya uundaji ya usambazaji wa hivi karibuni zaidi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector logs example.com --error

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye mazingira ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi ya mara moja vimebadilishwa. --access kwa ajili ya kumbukumbu ya ufikiaji, --build kwa ajili ya kumbukumbu ya uundaji wa usambazaji wa mwisho (tovuti ambayo haijaundwa na mtoa huduma wa uundaji huonyesha hatua za usambazaji wenyewe); bila bendera yoyote kumbukumbu zote mbili za tovuti huonyeshwa, na kumbukumbu ambayo haikuweza kusomwa hueleza hivyo badala ya kuonekana tupu


Error log — example.com
────────────────────────────────────────────────────────────

2026-09-14 11:06:07.153643 [NOTICE] [1929978] [T0] [config:vhost:zcaffb6eec5abbdab03fb9b2d62a15:epsr:lsphp-zcaffb6eec5abbdab03fb9b2d62a15]'Process Limit' probably is too low, adjust the limit to: 640.
2026-09-14 11:06:37.873060 [INFO] [1929982] [T0] [lsphp-zcaffb6eec5abbdab03fb9b2d62a15] add child process pid: 1933036, procinfo: 0x5555561cfe30

`zinnector wp`

Tekeleza amri ya WP-CLI iliyoruhusiwa kwenye tovuti.

zinnector wp [options] [command...]

hoja	inahitajika	ni nini
`command...`	hapana	amri ya WP-CLI na hoja zake, k.m. plugin list — iache kwa kutumia --commands

chaguo	inachofanya	chaguo-msingi
`-s, --site <site>`	id ya tovuti au kikoa
`--commands`	orodhesha kile jukwaa litakachoendesha
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector wp plugin list --site example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. orodha iliyoruhusiwa inatolewa na jukwaa — zinnector wp --commands huichapisha

name	status	update	version	update_version	auto_update
akismet	inactive	none	5.7.2		off
hello	inactive	none	1.7.2		off
imunify-security	active	none	4.1.0		off
litespeed-cache	active	none	7.9.1		off
redis-cache	active	none	2.8.0		off
zinn-cache	active	none	1.2.2		off
object-cache.php	dropin				off

`zinnector backup`

Orodhesha na chukua nakala rudufu za tovuti.

zinnector backup [options] [command]

Mfano

zinnector backup list example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho (ids) na viungo vya matumizi moja vimebadilishwa. backup peke yake huchapisha amri zake ndogo; tazama backup list na backup now hapa chini


Backups — example.com  ·  3
───────────────────────────────────────────────────────────
status  taken                        size    id
stored  2026-09-14T09:06:39.918280Z  4.7 MB  01a00000-0000-7000-8000-000000000000
stored  2026-09-14T01:29:20.403161Z  36 MB   01a00001-0000-7000-8000-000000000001
stored  2026-09-14T01:29:15.898099Z  36 MB   01a00002-0000-7000-8000-000000000002

daily backups   on
retention       30 days
off-site copy   yes
on-demand left  2 of 3

`zinnector backup list`

Orodhesha nakala rudufu za tovuti na kile ambacho mpango wake unatoa.

zinnector backup list [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa kwenye zinnector.json

chaguo	inachofanya	chaguo-msingi
`--json`	matokeo yanayosomeka na mashine

Mfano

zinnector backup list example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Backups — example.com  ·  3
───────────────────────────────────────────────────────────
status  taken                        size    id
stored  2026-09-14T09:06:39.918280Z  4.7 MB  01a00000-0000-7000-8000-000000000000
stored  2026-09-14T01:29:20.403161Z  36 MB   01a00001-0000-7000-8000-000000000001
stored  2026-09-14T01:29:15.898099Z  36 MB   01a00002-0000-7000-8000-000000000002

daily backups   on
retention       30 days
off-site copy   yes
on-demand left  2 of 3

`zinnector backup now`

Fanya nakala rudufu kulingana na mahitaji.

zinnector backup now [options] [site]

hoja	inahitajika	ni nini
`site`	hapana	id ya tovuti, kikoa kikuu au jina — chaguo-msingi ni tovuti iliyounganishwa katika zinnector.json

Mfano

zinnector backup now example.com

Unachokiona

✔ backup started — zinnector backup list example.com shows it when it completes

`zinnector domains`

Orodhesha vikoa ambavyo ufunguo huu unaweza kuona.

zinnector domains [options]

chaguo	kile inachofanya	chaguo-msingi
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector domains

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Domains  ·  1
──────────────
domain       status     ownership  renewal        expires
example.com  connected  connected  no auto-renew  —

`zinnector dns`

Soma na ubadilishe rekodi za DNS.

zinnector dns [options] [command]

Mfano

zinnector dns list example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. dns peke yake huonyesha amri zake ndogo; tazama dns list, dns add na dns rm hapa chini


DNS — example.com  ·  1 records
────────────────────────────────────────
type  name          value               ttl
TXT   w4357-verify  zinn-w4357-updated  ttl 3600

`zinnector dns list`

Orodhesha rekodi za DNS za kikoa.

zinnector dns list [options] <domain>

hoja	inahitajika	ni nini
`domain`	ndiyo	kikoa, kwa jina au id

chaguo	inachofanya	chaguomsingi
`--type <type>`	rekodi za aina hii pekee
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector dns list example.com

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


DNS — example.com  ·  1 records
────────────────────────────────────────
type  name          value               ttl
TXT   w4357-verify  zinn-w4357-updated  ttl 3600

`zinnector dns add`

Tengeneza rekodi ya DNS.

zinnector dns add [options] <domain> <type> <name> <value>

hoja	inahitajika	ni nini
`domain`	ndiyo	kikoa, kwa jina au id
`type`	ndiyo	aina ya rekodi: A, AAAA, CNAME, MX, TXT, SRV, …
`name`	ndiyo	jina la rekodi — @ kwa kikoa chenyewe, au lebo ya kikoa kidogo
`value`	ndiyo	kile ambacho rekodi inaelekeza — anwani, jina la seva au maandishi

chaguo	inachofanya	chaguomsingi
`--ttl <seconds>`	muda wa kuishi (time to live)	`"3600"`
`--priority <n>`	kipaumbele, kwa MX na SRV
`--proxied`	elekeza kupitia CDN
`-y, --yes`	usiulize

Mfano

zinnector dns add example.com TXT _acme "token" --ttl 300

Unachokiona — rekodi huonyeshwa na kuthibitishwa kabla ya kuandikwa; pitisha --yes ili kuruka swali

Add a DNS record to example.com
───────────────────────────────

  type   TXT
  name   _acme
  value  "token"
  ttl    300

  create it? [y/N] y
✔ created TXT _acme

`zinnector dns rm`

Futa rekodi ya DNS.

zinnector dns rm [options] <domain> <recordId>

hoja	inahitajika	ni nini
`domain`	ndiyo	kikoa, kwa jina au id
`recordId`	ndiyo	id ya rekodi, kama inavyochapishwa na zinnector dns list

chaguo	inachofanya	chaguo-msingi
`-y, --yes`	usiombe uthibitisho

Mfano

zinnector dns rm example.com rec_7f3a

Unachokiona

⚠ deleting A @ 203.0.113.10 from example.com
  delete it? [y/N] y
✔ deleted

`zinnector mail`

Orodhesha huduma za barua pepe.

zinnector mail [options]

chaguo	kile inachofanya	chaguo-msingi
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector mail

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 kwenye uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa


Mail services  ·  0
────────────────────

● no mail services

`zinnector bulk`

Endesha operesheni moja kwenye tovuti nyingi (cache_purge, malware_scan, sitemap, block_ip).

zinnector bulk [options] <operation>

hoja	inahitajika	ni nini
`operation`	ndiyo	cha kuendesha kwenye kila tovuti iliyochaguliwa: cache_purge, malware_scan, sitemap au block_ip

chaguo	inachofanya	chaguomsingi
`--all`	kila tovuti ambayo ufunguo huu unaweza kuona
`--site <site...>`	tovuti maalum, kwa id au kikoa
`--status <status>`	kila tovuti iliyo katika hali hii
`-y, --yes`	usiulize
`--json`	matokeo yanayosomeka kwa mashine

Mfano

zinnector bulk cache_purge --all

Unachokiona — kimenaswa kutoka kwa utekelezaji halisi wa 0.1.5 dhidi ya uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. wito mmoja kwenye jukwaa kwa uteuzi mzima, sio mmoja kwa kila tovuti; uteuzi unaonyeshwa na kuthibitishwa kwanza


Bulk cache_purge  ·  1 sites
─────────────────────────────

·   example.com

→ running cache_purge
✔ cache_purge accepted for 1 sites

  The platform runs this asynchronously; results appear per site in the dashboard.

`zinnector ai`

Uliza msaidizi wa Zinn Digital®, ukitumia mradi huu kama muktadha.

zinnector ai [options] <question...>

hoja	inahitajika	ni nini
`question...`	ndiyo	kile unachotaka kuuliza, kwa maneno rahisi — kuweka alama za nukuu ni hiari

chaguo	inachofanya	chaguomsingi
`-s, --site <site>`	uliza kuhusu tovuti mahususi
`--org <id>`	shirika la kuuliza kama hilo, wakati akaunti yako ni ya zaidi ya moja
`--no-context`	usitume chochote kuhusu mradi wa ndani
`--json`	matokeo yanayosomwa na mashine

Mfano

zinnector ai "why is my deploy failing?"

Unachokiona — kimenaswa kutoka kwa uendeshaji halisi wa 0.1.5 katika uzalishaji mnamo 2026-09-14; vikoa, vitambulisho na viungo vya matumizi moja vimebadilishwa. Msaidizi anajibu kwa lugha ya AKAUNTI — lugha ya akaunti hii ni Kiarabu, kwa hivyo jibu lililonaswa ni la Kiarabu kwa swali la Kiingereza

→ thinking

Zinn Digital® assistant
────────────────────────────

  هذا مشروع WordPress تم إنشاؤه بواسطة Zinnector® (مُهيّأ على PHP 8.4، أحدث
  إصدار WordPress، وبيئة تشغيل playground)؛ لتشغيله محلياً، انتقل إلى مجلده
  وشغّل الأمر: cd <اسم-المشروع> ثم zinnector dev، وسيقوم بتشغيل موقع WordPress
  حقيقي على جهازك دون الحاجة إلى Docker.

  sources:
    · https://zinndigital.com/kb/zinnector-getting-started
    · https://zinndigital.com/kb/zinnector-local-development

`zinnector mcp`

Endesha daraja la stdio kwenye seva ya MCP iliyopangishwa — kwa ajili ya Claude Desktop na wateja wengine wa ndani tu.

zinnector mcp [options]

Mfano

ZINN_MCP_TOKEN=zmcp_live_… zinnector mcp

Unachokiona — kimeanzishwa NA mteja wa AI kama vile Claude Desktop, kamwe si kwa mkono — kinatumia MCP kwenye stdin na stdout. Imethibitishwa kutoka kwa Claude Code 2.1.270 dhidi ya seva ya moja kwa moja mnamo 2026-09-12

zinnector 0.1.4: MCP bridge to https://api.zinndigital.com/v1/mcp

Vigezo vya mazingira

kigezo	athari
`ZINNECTOR_TOKEN`	ufunguo wa API, unaotumika badala ya wasifu uliohifadhiwa — hivi ndivyo CI inavyothibitisha
`ZINNECTOR_API`	URL ya msingi ya API (chaguo-msingi `https://api.zinndigital.com`)
`ZINNECTOR_DEBUG=1`	chapisha stack traces na matokeo binafsi ya kisakinishi cha runtime
`ZINNECTOR_CACHE_DIR`	mahali ambapo runtime ya WordPress na Node yoyote inayosimamiwa huwekwa (chaguo-msingi `~/.cache/zinnector`)
`ZINNECTOR_CONFIG_DIR`	mahali faili ya wasifu wa ufunguo wa API inapoishi (chaguo-msingi `~/.config/zinnector`)
`NO_COLOR`	lemaza rangi

Misimbo ya kutoka

0 mafanikio · 1 ugunduzi au ukataaji · 70 hitilafu ya ndani · 77 uthibitishaji au ruhusa · 78 Node isiyotumika.

Nyaraka zote za watengenezaji →

Mapya kutoka kwenye blogu

Tulichoandika kuhusu upangishaji, SEO na uendeshaji wa tovuti kwa kiwango kikubwa.

SEO na Ujenzi wa Viungo kutoka Tabaka la Upangishaji: Mtazamo wa Mwendeshaji wa Mwaka 2026

Jinsi huduma ya upangishaji tovuti inavyounda uwekaji fahirisi na thamani ya viungo (link equity) mnamo 2026: kuweka kurasa zikiwa kwenye fahirisi, kukagua vikoa vya zamani kabla ya kuvitumia, ujenzi wa viungo bila kuacha athari (footprint), na ukweli kuhusu kile ambacho miundombinu inaweza na haiwezi kufanya kwa ajili ya SEO.

21 Julai 2026

Soma chapisho →

Kufanya WordPress Kuwa ya Kasi na Salama: Orodha Hakiki ya Utendaji na Programu-jalizi

Orodha hakiki ya vitendo kwa ajili ya WordPress ya haraka na salama: uhifadhi wa data wa muda katika kiwango cha seva, akiba ya vitu kwa kila tovuti, programu-jalizi chache zinazofaa kutumiwa, kusasisha mfumo wa teknolojia, na kurasa za WooCommerce ambazo hupaswi kamwe kuzihifadhi kwenye akiba.

20 Julai 2026

Soma chapisho →

Jinsi ya Kuchagua Upangishaji Wavuti Unaosimamiwa mnamo 2026: Mwongozo wa Mnunuzi

Kile kinachotofautisha kihalisi upangishaji mzuri unaosimamiwa na kisanduku cha bei nafuu chenye paneli ya kudhibiti — uhamiaji, nakala rudufu, utenganishaji, uhifadhi halisi wa kache na upanuzi wa kuaminika — na jinsi ya kuuhukumu kabla ya kujitolea.

19 Julai 2026

Soma chapisho →

Soma blogu →

Bado umekwama?

Usaidizi umejumuishwa kwenye kila mpango, huduma ya msaada iko wazi saa 24 kwa siku, na unaweza kutuandikia kwa lugha yoyote kati ya lugha zetu 58 — tunakujibu kwa lugha yako.

Wasiliana na usaidizi → Makala yote →