Zinnector® CLI

Gbogbo àṣẹ, taara láti inú --help

Zinnector® 0.1.2 kọ oju opo wulo WordPress sori kọmputa rẹ pẹlu ohunkohun ti a fi sori ẹrọ bikoṣe Node, ṣayẹwo rẹ lodi si iho alejo gbigba ti o fẹ lati ran lọwọ, ati titari. Oju-iwe yii ni ipilẹṣẹ lati awọn asọye aṣẹ ti CLI funrararẹ — awọn nkan kanna zinnector --help tẹjade lati — nitorinaa ko le yato si ohun elo ti o ti fi sori ẹrọ.

Àwọn àṣẹ 36 nínú Zinnector® 0.1.2.

Fi sori ẹ

Àṣẹ kan, lórí Node 24 tàbí tuntun jù lọ. Ọ̀fẹ́ àti wí pé ó ní ìwé-àṣẹ MIT; ìgbékalẹ̀ àti ṣíṣe tíkòtì sí ojú-wẹ̀bù ní agbègbè rẹ kò nílò àkọọ́lẹ̀ kankan rárá.

npm install -g zinnector

Nọ́dù {node} tàbí tuntun ju bẹ́ẹ̀ lọ

Ṣiṣẹ node --version jade; o gbọdọ tẹ v24 tabi ju bẹẹ lọ jade. Fi LTS lọwọlọwọ sori ẹrọ lati nodejs.org — lori Windows, winget install OpenJS.NodeJS.LTS; lori macOS, brew install node@24.

Njẹ o ti ri EBADENGINE ri?

Yẹn ni npm n sọ fun ọ pe Node rẹ ti dagba ju 24 lọ. Ṣugbọn fifi sori ẹrọ naa pari, ṣugbọn CLI kọ lati ṣiṣẹ ati sọ bẹẹ. Ṣe imudojuiwọn Node ki o tun fi sori ẹrọ lẹẹkansi.

Ṣé o wà lórí Node 26 tàbí tuntun jù lọ?

CLI naa nṣiṣẹ daadaa. Ẹrọ ṣiṣe WordPress ti o ṣe igbasilẹ ni module abinibi kan pẹlu awọn alakọbẹrẹ ti a ti kọ tẹlẹ fun Node 24 ati 25 nikan, nitorinaa lori lilo akọkọ Zinnector® tun gba Node 24 fun akoko ṣiṣe nikan - nipa 30 MB, ti a rii daju lodi si awọn iṣayẹwo checksums nodejs.org. Ko si olupilẹṣẹ, ko si Visual Studio, ko si ohun ti o le ṣe pẹlu ọwọ.

Ṣe idanwo rẹ̀ láti rí i pé ó ń ṣiṣẹ́ — ìṣẹ́jú méjì, kò sí àkọọ́lẹ̀

Ṣe àwọn wọ̀nyí ní ìtòlẹ́sẹẹsẹ. Lábẹ́ Ọ̀kọ̀ọ̀kan ni ohun tí àṣeyọrí rẹ jọ, nítorí náà o mọ àkókò tí nǹkan kan bá ti ba jẹ́.

  1. Fi sori ẹ

    npm install -g zinnector

    Àṣeyọrí: npm parí láìsí ìkìlọ̀ EBADENGINE kankan.

  2. Ṣayẹwo ẹ̀yà náà

    zinnector --version

    Àṣeyọrí: nọ́mbà ẹ̀dà kan. Lórí Node tó jẹ́ àtijọ́ ju 24 lọ, ó ń tẹ̀ jáde ìfiránṣẹ́ kan tó sọ pé Node 24 tàbí tuntun ni a nílò, ó sì ń jáde kúrò dípò bẹ́ẹ̀.

    0.1.2
  3. Ka iranlọwọ náà

    zinnector --help

    Aseyori: asia kan to n pe awọn aṣẹ marun ti sisan naa, lẹhinna aṣẹ kọọkan pẹlu idi laini kan — atọkọ lori oju-iwe yii.

      new       scaffold a WordPress project you can run immediately
      dev       run this project locally — no Docker required
      login     sign in — with your own account in the browser, or with an API key
      logout    forget a stored sign-in
      whoami    show who this CLI is signed in as, and what it can reach
      …
  4. Gbe aaye kalẹ

    zinnector new my-site

    Àṣeyọrí: àkọlé kan "Created my-site", àwọn fáìlì tí ó kọ, àti àwọn àṣẹ tí ó kàn látiáṣe. Kò sí ohun tí ó wà nínú rẹ̀ tí ó jẹ́ ààyè ìfi pamọ́.

    Created my-site  ·  site
      + zinnector.json
      + wp-content/…
    → run it:
        cd my-site
        zinnector dev
  5. Lo

    cd my-site
    zinnector dev

    Ìgbà àkọ́kọ́ tí yóò ṣiṣẹ́, yóò béèrè lẹ́ẹ̀kan ṣoṣo láti ṣe igbasilẹ̀ ẹ̀rọ WordPress (bii 570 MB, tí a tọ́jú sínú àkópọ̀ ìpamọ́ ara Zinnector®). Aṣeyọri: ìlà “running at” pẹlu adirẹsi agbegbe kan.

    ✔ running at http://127.0.0.1:9400
      admin: http://127.0.0.1:9400/wp-admin  (already signed in)
  6. Ṣii lori aṣàwákiri kan

    open http://127.0.0.1:9400

    Aseyori: aaye WordPress tuntun kan ti a pe ni “My WordPress Website”, ati /wp-admin ṣii daṣibọọdù ti a ti wọle tẹlẹ. Fi pLọgbin sinu wp-content/plugins ati pe o wa nibẹ ni atunkọ ti o tẹle.

    Gbogbo ohun ti o wa loke n ṣiṣẹ laisi akọọlẹ kan. Ijọpọ, iṣaju-ofurufu ati titari nilo bọtini API kan lati daaṣibọọdu rẹ ati aaye kan lori gbigbalejo Zinn Digital®.

Ìṣàn iṣẹ́ náà: dá, ṣe ìdàgbàsókè, sopọ̀, ṣàyẹ̀wò, tì síwájú

Àwọn àṣẹ mẹ́fà láti ìbẹ̀rẹ̀ dé ojú-wọ̀ṣọ́ tó ń ṣiṣẹ́. zinnector new tẹ àkójọ yìí jáde nígbà tí ó bá parí, nítorí náà o kò nílò láti sọ ọ́ sọ́kàn rẹ tàbí láti rántí rẹ̀ rárá.

zinnector new my-site      # scaffold a project that boots immediately
cd my-site
zinnector dev              # a real WordPress, locally, with no Docker

zinnector login            # once, when you have hosting
zinnector link             # point the project at a slot
zinnector check            # pre-flight: what will NOT match on the slot?
zinnector push             # push your commits, deploy, watch it finish

Ohun aarin ni aaye náà. Ìṣẹ̀wò zinnector check fi ohun tí o kọ́ — ẹ̀yà PHP, disk, iye fáìlì, ẹ̀yà WordPress — wé ohun ti o fẹ́ gbé e sí, ó sọ gbogbo àìbámu ati gbogbo àfiwé ti ko le ṣe, lẹhin na o jẹ ki o gbe e kalẹ síbẹẹ, nitori o mọ awọn nkan nipa aaye rẹ ti oluyẹwo ko mọ.

Atọka àṣẹ

Gbogbo 36 awọn aṣẹ, ni aṣẹ ti zinnector --help ṣe akojọ wọn. Awọn abajade ti a samisi bi “ti a mu” ni a lẹ mọ lati ęsẹ gidi ti ẹya yii; awọn iyoku fihan apẹrẹ gangan ti aṣẹ naa tẹjade, pẹlu awọn iye apẹẹrẹ — awọn ìpínlẹ̀ rẹ, awọn id ati awọn nọmba yoo yato.

Àwọn àṣàyàn gbogbo gbòò, tí a gbà ṣáájú àṣẹ èyíkéyìí:

ÀṣàyànOhun tí ó ń ṣe
-V, --versionprint the version
--profile <name>use a named credential profile
-h, --helpFi iranlọwọ han fun eyikeyi aṣẹ.

zinnector new

scaffold a WordPress project you can run immediately

zinnector new [options] [name]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
namekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
-t, --template <kind>one of: site, plugin, theme"site"
--php <version>PHP version to develop against"8.3"
--wp <version>WordPress version for the local runtime"latest"
--runtime <name>playground or docker"playground"
--herescaffold into the current directory instead of a new one

Apẹẹrẹ

zinnector new my-site

Ohun tí o rícaptured — 0.1.2 on 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

run this project locally — no Docker required

zinnector dev [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--php <version>PHP version to run (5.2–8.5 on playground, 7.4–8.5 on docker)
--wp <version>WordPress version
-p, --port <port>port to serve on
--runtime <name>playground (default) or docker
--loginlog in as admin automaticallytrue
--no-logindo not log in automatically
--onceboot, report what is running, then stop
--yesinstall the local runtime without asking
--reset-runtimedelete the installed runtime and install it again
-v, --verboseshow the runtime's own output

Apẹẹrẹ

cd my-site
zinnector dev

Ohun tí o rícaptured — 0.1.2. The first run asks once to download the WordPress runtime (~570 MB); pass --yes to skip the question

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

sign in — with your own account in the browser, or with an API key

zinnector login [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--profile <name>store under a named profile"default"
--api <url>API base URL"https://api.zinndigital.com"
--api-keypaste a per-organisation API key instead of signing in as yourself
--issuer <url>the sign-in service"https://auth.zinndigital.com/realms/zinn"
--no-browserprint the sign-in link without trying to open a browser

Apẹẹrẹ

zinnector login

Ohun tí o ríthe key is typed at the prompt, never on the command line. In CI, pipe it: 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

forget a stored sign-in

zinnector logout [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--profile <name>which profile to forget"default"

Apẹẹrẹ

zinnector logout

Ohun tí o rí

✔ signed out of profile “default”

zinnector whoami

show who this CLI is signed in as, and what it can reach

zinnector whoami [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--profile <name>use a named profile
--scopeslist the permissions an API key carries
--jsonmachine-readable output

Apẹẹrẹ

zinnector whoami --scopes

Ohun tí o rí

Signed in  ·  https://api.zinndigital.com
─────────────────────────────────────────

  key           zdk_live_…3f9a
  organisation  Acme Ltd
  profile       default

  · sites.read
  · sites.deploy
  · dns.manage

zinnector sites

list the sites this key can see

zinnector sites [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output
--status <status>only sites in this status

Apẹẹrẹ

zinnector sites

Ohun tí o rí

Sites  ·  2
───────────

  domain        status   php      target  id
  example.com   active   php 8.3  fleet   01a03f39-730a-7dc4-84b0-5d4f7582dd04
  shop.test     active   php 8.2  fleet   01a03f39-9c11-7b02-a7e0-2e4d0c5f1b77

zinnector status

everything the platform knows about one site

zinnector status [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector status example.com

Ohun tí o rí

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

  status        active
  product line  mainstream
  stack         wordpress

● PHP
  version   8.3
  applied   yes

● Quota
  disk      412 MB of 10 GB
  files     18,204 of 250,000

● Deploy
  repository  acme/example-site (main)
  last        2 hours ago — success

zinnector share

give one person access to ONE site — a developer, a designer, a client

zinnector share [options] <site> <email>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
siteBẹẹni
emailBẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--role <role>what they may do: viewer, editor, manager
--reason <text>why they need it — kept with the grant for the audit trail
--until <date>when access ends on its own (YYYY-MM-DD); omit for until-revoked
--jsonmachine-readable output

Apẹẹrẹ

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

Ohun tí o ríthe exact shape the command prints, from the source (W40-DEVTOOL added these after this file was last captured); your domains, ids and dates will differ

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

who has been given access to a site, and whether they have accepted

zinnector collaborators [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector collaborators example.com

Ohun tí o ríthe exact shape the command prints, from the source (W40-DEVTOOL added these after this file was last captured); your domains, ids and dates will differ

Access to example.com  ·  2
────────────────────────────

  who               role    status                      ends              why                   grant
  dev@agency.test   editor  invited — not yet accepted  —                 rebuild the checkout  01a03f39-9c11-7b02-a7e0-2e4d0c5f1b77
  ana@studio.test   viewer  active                      until 2026-12-31  quarterly audit       01a03f39-af52-7e19-93c1-6b0d2a7c4e11

zinnector unshare

take a person's access to a site back — by email or grant id

zinnector unshare [options] <site> <who>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
siteBẹẹni
whoBẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--yesdo not ask

Apẹẹrẹ

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

Ohun tí o ríthe exact shape the command prints, from the source (W40-DEVTOOL added these after this file was last captured); your domains, ids and dates will differ

✔ withdrew the invitation to dev@agency.test

zinnector invitations

the invitations waiting for you, and accept one

zinnector invitations [options] [command]

Apẹẹrẹ

zinnector invitations

Ohun tí o ríthe exact shape the command prints, from the source (W40-DEVTOOL added these after this file was last captured); your domains, ids and dates will differ; with no subcommand it runs `list`

Invitations  ·  1
──────────────────

  Acme Ltd has shared example.com with you as editor  01a03f39-9c11-7b02-a7e0-2e4d0c5f1b77

→ accept one: zinnector invitations accept <id>

zinnector invitations list

invitations addressed to the account you are signed in as

zinnector invitations list [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector invitations list

Ohun tí o ríthe exact shape the command prints, from the source (W40-DEVTOOL added these after this file was last captured); your domains, ids and dates will differ

Invitations  ·  1
──────────────────

  Acme Ltd has shared example.com with you as editor  01a03f39-9c11-7b02-a7e0-2e4d0c5f1b77

→ accept one: zinnector invitations accept <id>

zinnector invitations accept

accept an invitation — the site is yours the moment this returns

zinnector invitations accept [options] <id>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
idBẹẹni

Apẹẹrẹ

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

Ohun tí o ríthe exact shape the command prints, from the source (W40-DEVTOOL added these after this file was last captured); your domains, ids and dates will differ

✔ you now have access to example.com

zinnector pull

pull a hosted site's files into this project for local dev — and re-run to re-sync

zinnector pull [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--via <seam>auto (default), git, or backup"auto"
--freshtake a new backup rather than using the latest one (spends an on-demand slot)
--max-age <hours>accept the latest backup if it is younger than this"24"
--fullthe whole document root, WordPress core included (default: wp-content only)
--no-uploadsleave wp-content/uploads (media) behind
--live-configalso write wp-config.php — it holds the LIVE database credentials
--cleanempty wp-content before extracting, so deletions on the site are mirrored
--dry-runsay what would happen and stop
--yesdo not ask

Apẹẹrẹ

zinnector pull

Ohun tí o rí

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

make a local project from a hosted site: clone its repository or pull its files

zinnector clone [options] <site> [dir]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
siteBẹẹni
dirkò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--via <seam>auto (default), git, or backup"auto"
--freshtake a new backup rather than using the latest one
--fullthe whole document root, WordPress core included
--no-uploadsleave wp-content/uploads (media) behind
--live-configalso write wp-config.php — it holds the LIVE database credentials
--yesdo not ask

Apẹẹrẹ

zinnector clone client.example.com

Ohun tí o rí

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 check

compare this project against the slot you are about to deploy to

zinnector check [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--probeboot the local runtime and MEASURE its php, rather than trusting zinnector.json
--allshow passing checks too
--strictalso fail when something could not be checked
--jsonmachine-readable output

Apẹẹrẹ

zinnector check

Ohun tí o rícaptured from a real run against a slot on PHP 7.4 — the whole point of the command

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

  local   php 8.3   1,284 files, 12.4 MB
  slot    php 7.4.33   target fleet
  local php is the version DECLARED in zinnector.json — run with --probe to measure it

  ✖ high      php 8.3 locally, 7.4 on the slot
      You built against PHP 8.3, which is newer than the PHP 7.4 the
      slot runs. Code that uses syntax or functions added after the
      slot's version will fatal at runtime, not at deploy time.
      try zinnector php 8.3

  ⚠ warn      the slot runs php 7.4, which is past end of life
      try zinnector php --list

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

  5 passed  ·  3 to look at  ·  2 could not be checked

  none of this blocks a deploy — zinnector push --force proceeds anyway

zinnector push

pre-flight, push your commits, and deploy

zinnector push [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
-f, --forcedeploy even when pre-flight has findings
--skip-checksdo not run pre-flight at all
--probemeasure the local runtime during pre-flight instead of trusting zinnector.json
--no-waittrigger the deploy and exit without watching it
--no-gitdo not run git push; deploy whatever the platform already has
--dry-rundo everything except the deploy

Apẹẹrẹ

zinnector push

Ohun tí o rí

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

redeploy what the platform already has, without pushing

zinnector deploy [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--no-waittrigger and exit

Apẹẹrẹ

zinnector deploy example.com

Ohun tí o rí

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

● deploy 7c0e… started — watching
✔ deployed 4f1c2a9b in 41s

zinnector deploys

a site's deploy history

zinnector deploys [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output
-n, --limit <n>how many to show"10"

Apẹẹrẹ

zinnector deploys example.com

Ohun tí o rí

Deploys — example.com  ·  3
───────────────────────────

  status   commit    branch  trigger  started        message
  success  4f1c2a9b  main    cli      2 hours ago    add the contact form
  success  b21d70e4  main    push     yesterday      fix footer links
  failed   9e8a0c13  main    push     3 days ago     build: composer install exited 1

zinnector php

show or switch a site's PHP version

zinnector php [options] [version]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
versionkò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
-s, --site <site>site id or domain
--listlist the versions the platform offers
--jsonmachine-readable output

Apẹẹrẹ

zinnector php 8.3 --site example.com

Ohun tí o ríwith no version it shows the current one; --list shows what the platform offers for this site's product line

PHP — example.com
─────────────────

  version   7.4  →  8.3
  applied   the machine will confirm shortly

  switch example.com to php 8.3? [y/N] y
✔ php 8.3 requested
⚠ recorded, but the machine has not confirmed it yet

zinnector quota

disk, files and database usage against what the plan grants

zinnector quota [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector quota example.com

Ohun tí o rí

Quota — example.com
───────────────────

  disk      412 MB of 10 GB   (4%)
  files     18,204 of 250,000 (7%)
  database  38 MB of 1 GB     (4%)

zinnector db

database size, and single-use links into phpMyAdmin and the file manager

zinnector db [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector db example.com

Ohun tí o ríthe phpMyAdmin and file-manager links are single-use and expire; do not paste them anywhere

Database — example.com
──────────────────────

  engine      mariadb 10.11
  size        38 MB
  phpmyadmin  https://…/pma/sso?token=… (single use)
  files       https://…/files/sso?token=… (single use)

zinnector logs

tail a site's access and error logs

zinnector logs [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--accessonly the access log
--erroronly the error log
--buildthe build log of the most recent deploy instead
--jsonmachine-readable output

Apẹẹrẹ

zinnector logs example.com --error

Ohun tí o rí--access for the access log, --build for the last deploy's build log; with no flag both site logs are shown

Error log — example.com
───────────────────────
[06-Sep-2026 10:12:44 UTC] PHP Warning:  Undefined variable $x in /wp-content/plugins/my-plugin/my-plugin.php on line 12

zinnector wp

run an allow-listed WP-CLI command on a site

zinnector wp [options] <command...>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
command...Bẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
-s, --site <site>site id or domain
--commandslist what the platform will run
--jsonmachine-readable output

Apẹẹrẹ

zinnector wp plugin list --site example.com

Ohun tí o ríthe allow-list is served by the platform — zinnector wp --commands prints it

+-----------------+----------+--------+---------+
| name            | status   | update | version |
+-----------------+----------+--------+---------+
| my-plugin       | active   | none   | 1.0.0   |
| zinn-cache      | active   | none   | 2.4.1   |
+-----------------+----------+--------+---------+

zinnector backup

list and take site backups

zinnector backup [options] [command]

Apẹẹrẹ

zinnector backup list example.com

`backup` on its own prints its subcommands; see `backup list` and `backup now` below

zinnector backup list

list a site's backups and what its plan grants

zinnector backup list [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector backup list example.com

Ohun tí o rí

Backups — example.com  ·  3
───────────────────────────

  status     taken          size    id
  complete   today 03:00    412 MB  bk_01a0…
  complete   yesterday      410 MB  bk_019f…
  complete   2 days ago     409 MB  bk_019e…

  retention  30 days
  off-site   yes

zinnector backup now

take an on-demand backup

zinnector backup now [options] [site]
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
sitekò sí

Apẹẹrẹ

zinnector backup now example.com

Ohun tí o rí

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

zinnector domains

list the domains this key can see

zinnector domains [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector domains

Ohun tí o rí

Domains  ·  2
─────────────

  domain        status   registrar  renewal  expires
  example.com   active   zinn       auto     2027-03-14
  shop.test     active   external   —        —

zinnector dns

read and change DNS records

zinnector dns [options] [command]

Apẹẹrẹ

zinnector dns list example.com

`dns` on its own prints its subcommands; see `dns list`, `dns add` and `dns rm` below

zinnector dns list

list a domain's DNS records

zinnector dns list [options] <domain>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
domainBẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--type <type>only records of this type
--jsonmachine-readable output

Apẹẹrẹ

zinnector dns list example.com

Ohun tí o rí

DNS — example.com  ·  4 records
───────────────────────────────

  type  name   value            ttl
  A     @      203.0.113.10     300   rec_7f…
  A     www    203.0.113.10     300   rec_80…
  MX    @      10 mail.example.com  3600  rec_81…
  TXT   @      "v=spf1 -all"    3600  rec_82…

zinnector dns add

create a DNS record

zinnector dns add [options] <domain> <type> <name> <value>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
domainBẹẹni
typeBẹẹni
nameBẹẹni
valueBẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--ttl <seconds>time to live"3600"
--priority <n>priority, for MX and SRV
--proxiedroute through the CDN
-y, --yesdo not ask

Apẹẹrẹ

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

Ohun tí o ríthe record is shown and confirmed before it is written; pass --yes to skip the question

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

delete a DNS record

zinnector dns rm [options] <domain> <recordId>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
domainBẹẹni
recordIdBẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
-y, --yesdo not ask

Apẹẹrẹ

zinnector dns rm example.com rec_7f3a

Ohun tí o rí

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

zinnector mail

list mail services

zinnector mail [options]
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--jsonmachine-readable output

Apẹẹrẹ

zinnector mail

Ohun tí o rí

Mail services  ·  1
───────────────────

  domain        status   provider  mailboxes  dns
  example.com   active   zinn      3          ok

zinnector bulk

run one operation across many sites (cache_purge, malware_scan, sitemap, block_ip)

zinnector bulk [options] <operation>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
operationBẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
--allevery site this key can see
--site <site...>specific sites, by id or domain
--status <status>every site in this status
-y, --yesdo not ask
--jsonmachine-readable output

Apẹẹrẹ

zinnector bulk cache_purge --all

Ohun tí o ríone call to the platform for the whole selection, not one per site; the selection is shown and confirmed first

Bulk cache_purge  ·  2 sites
────────────────────────────
  · example.com
  · shop.test

  run cache_purge on 2 sites? [y/N] y
✔ cache_purge queued for 2 sites

zinnector ai

ask the Zinn Digital assistant, with this project as context

zinnector ai [options] <question...>
AriyanjiyanGbọdọ jẹOhun tí ó ń ṣe
question...Bẹẹni
ÀṣàyànOhun tí ó ń ṣeÀiyipada
-s, --site <site>ask about a particular site
--no-contextdo not send anything about the local project
--jsonmachine-readable output

Apẹẹrẹ

zinnector ai "why is my deploy failing?"

Ohun tí o ríruns on the platform against your own account; from inside a project it sends the project's shape and site id, never file contents

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

Your last deploy of example.com failed at the build step: `composer install` exited 1 because
`vendor/` is committed alongside a lock file that no longer matches it. Remove `vendor/` from
the repository or run `composer update` and commit the new lock file, then `zinnector push`.

Tẹ́síwàá láti kàá

Fi sori ẹ fẹ́rẹ̀ẹ́ lẹ́sẹ̀ kankan kí o sì bẹ̀rẹ̀ ojú òpó wẹ́bù kan láàárín ìṣẹ́jú tó ń bọ̀

Ọfẹ, ti a ni iwe-ašẹ labẹ MIT, ati pe gbogbo aṣẹ jẹ iṣẹ abẹ labẹ akọọlẹni ti gbogbo eniyan le lo — ko si ohun ti o wa nibi ti o le ṣe ohun ti API ko le ṣe.

npm install -g zinnector