Zinnector® CLI

Duk umarni, kai tsaye daga --help

Zinnector® 0.1.2 yana gina shafin WordPress akan na'urarka ta kanka ba tare da an sanya komai ba sai Node, yana duba shi da wurin karɓar baƙi da za ku tura zuwa gare shi, kuma yana tura shi. An samar da wannan shafin daga bayanan umarnin CLI da kansa — abubuwa iri ɗaya waɗanda zinnector --help ke bugawa — don haka ba zai iya sabawa kayan aikin da kuka sanya ba.

Umarnin 36 a cikin Zinnector® 0.1.2.

Sanya shi

Umurni guda daya, a kan Node 24 ko sabo. Kyauta kuma mai lasisin MIT; ginawa da sarrafa shafin a gida baya buƙatar asusu ko kaɗan.

npm install -g zinnector

Node {node} ko mafi sabuntawa

Gudanar da node --version; dole ne ya nuna v24 ko sama da haka. Sanya LTS na yanzu daga nodejs.org — a kan Windows, winget install OpenJS.NodeJS.LTS; a kan macOS, brew install node@24.

Kun ga EBADENGINE?

Wannan shine abin da npm ke gaya maka cewa Node ɗinka ya fi 24 tsohuwa. Shigarwar ta kammala duk da haka, amma CLI ta ƙi gudana kuma ta bayyana haka. Haɓaka Node sannan ka sake shigarwa.

Kuna kan Node 26 ko sabon abu?

CLI na aiki lafiya. Abin da yake gudana na WordPress da yake saukarwa yana da wani nau'i na asali tare da tsararrun binary don Node 24 da 25 kawai, don haka a lokacin amfani na farko Zinnector® yana kuma samo Node 24 don abin da yake gudana kawai - kusan MB 30, wanda aka tabbatar da checksums na nodejs.org. Babu mai tara bayanai (compiler), babu Visual Studio, babu abin da za a yi da hannu.

Gwada yana aiki — mintoci biyu, babu asusu

Gudanar da wadannan a jere. A karkashin kowanne akwai abin da nasara ke nunawa, ta yadda za ku san lokacin da wani abu bai daidaita ba.

  1. Sanya shi

    npm install -g zinnector

    Nasara: npm ya gama ba tare da gargadin EBADENGINE ba.

  2. Bincika sigar

    zinnector --version

    Nasara: lambar sigar. A kan Node wanda ya fi 24 tsufa yana fitar da saƙo da ke cewa ana buƙatar Node 24 ko sabo, kuma yana fita maimakon haka.

    0.1.2
  3. Karanta taimako

    zinnector --help

    Nasara: wata tuta da ke nuna umarni biyar na kwararar, sannan kowane umarni tare da manufa mai layi ɗaya — lissafin da ke kan wannan shafin.

      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. Gina shafin

    zinnector new my-site

    Nasara: taken kai na “Created my-site”, fayilolin da ta rubuta, da kuma umarni na gaba da za a gudanar. Babu komai a ciki da yake madogara.

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

    cd my-site
    zinnector dev

    Farko yana tambaya sau ɗaya don sauke abin sarrafa WordPress (kimanin 570 MB, wanda aka ajiye a cikin rumbun adana bayanan Zinnector®). Nasara: layin “running at” tare da adireshin gida.

    ✔ running at http://127.0.0.1:9400
      admin: http://127.0.0.1:9400/wp-admin  (already signed in)
  6. Buɗe shi a cikin mai bincike

    open http://127.0.0.1:9400

    Nasara: sabon rukunin yanar gizo na WordPress mai suna "My WordPress Website", kuma /wp-admin yana buɗe allo na gudanarwa an riga an shiga. A zuba plugin a cikin wp-content/plugins kuma yana can a gaba wajen sabunta shafin.

    Komai na sama yana aiki ba tare da asusu ba. Haɗawa, kafin tashi da tura suna buƙatar maɓallin API daga allon sarrafa ku da kuma rukunin yanar gizo akan Zinn Digital® hosting.

Tsarin: ƙirƙira, ci gaba, haɗa, duba, tura

Umarni shida daga babu komai zuwa shafin yanar gizo mai aiki. zinnector new yana buga wannan lissafin lokacin da ya gama, don haka ba za a taba buƙatar tunawa da shi ba.

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

Wurin da ke tsakiya shi ne mahimmin abu. Dubawar zinnector tana kwatanta abin da kuka gina — sigar PHP, diski, adadin fayiloli, sigar WordPress — da wurin da kuke shirin tura wa, tana lissafa kowace saɓani da kowace kwatancen da ta kasa yi, sannan tana barin ku ku tura duk da haka, domin kun san abubuwa game da shafin ku wanda mai duba ba zai sani ba.

Jagorar umarni

Duk umarni 36, a cikin jerin da zinnector --help ya lissafa su. Abubuwan da aka fitar da aka yi musu alama da "captured" an manna su ne daga ainihin guduwar wannan sigar; sauran suna nunainihin sifar da umarnin ke bugawa, tare da misalan ƙima — yankunanka, lambobinka da adadi zasu bambanta.

Zaɓuɓɓuka na duniya, waɗanda ake karɓa kafin kowane umarni:

ZabiAbin da yake yi
-V, --versionprint the version
--profile <name>use a named credential profile
-h, --helpNuna taimako ga kowane umarni.

zinnector new

scaffold a WordPress project you can run immediately

zinnector new [options] [name]
HujjaAna buƙataAbin da yake yi
namebabu
ZabiAbin da yake yiNa asali
-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

Misali

zinnector new my-site

Abin da kake ganicaptured — 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]
ZabiAbin da yake yiNa asali
--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

Misali

cd my-site
zinnector dev

Abin da kake ganicaptured — 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]
ZabiAbin da yake yiNa asali
--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

Misali

zinnector login

Abin da kake ganithe 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]
ZabiAbin da yake yiNa asali
--profile <name>which profile to forget"default"

Misali

zinnector logout

Abin da kake gani

✔ signed out of profile “default”

zinnector whoami

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

zinnector whoami [options]
ZabiAbin da yake yiNa asali
--profile <name>use a named profile
--scopeslist the permissions an API key carries
--jsonmachine-readable output

Misali

zinnector whoami --scopes

Abin da kake gani

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]
ZabiAbin da yake yiNa asali
--jsonmachine-readable output
--status <status>only sites in this status

Misali

zinnector sites

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector status example.com

Abin da kake gani

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>
HujjaAna buƙataAbin da yake yi
siteE to
emailE to
ZabiAbin da yake yiNa asali
--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

Misali

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

Abin da kake ganithe 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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector collaborators example.com

Abin da kake ganithe 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>
HujjaAna buƙataAbin da yake yi
siteE to
whoE to
ZabiAbin da yake yiNa asali
--yesdo not ask

Misali

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

Abin da kake ganithe 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]

Misali

zinnector invitations

Abin da kake ganithe 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]
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector invitations list

Abin da kake ganithe 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>
HujjaAna buƙataAbin da yake yi
idE to

Misali

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

Abin da kake ganithe 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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--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

Misali

zinnector pull

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
siteE to
dirbabu
ZabiAbin da yake yiNa asali
--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

Misali

zinnector clone client.example.com

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--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

Misali

zinnector check

Abin da kake ganicaptured 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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
-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

Misali

zinnector push

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--no-waittrigger and exit

Misali

zinnector deploy example.com

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--jsonmachine-readable output
-n, --limit <n>how many to show"10"

Misali

zinnector deploys example.com

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
versionbabu
ZabiAbin da yake yiNa asali
-s, --site <site>site id or domain
--listlist the versions the platform offers
--jsonmachine-readable output

Misali

zinnector php 8.3 --site example.com

Abin da kake ganiwith 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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector quota example.com

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector db example.com

Abin da kake ganithe 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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--accessonly the access log
--erroronly the error log
--buildthe build log of the most recent deploy instead
--jsonmachine-readable output

Misali

zinnector logs example.com --error

Abin da kake gani--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...>
HujjaAna buƙataAbin da yake yi
command...E to
ZabiAbin da yake yiNa asali
-s, --site <site>site id or domain
--commandslist what the platform will run
--jsonmachine-readable output

Misali

zinnector wp plugin list --site example.com

Abin da kake ganithe 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]

Misali

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]
HujjaAna buƙataAbin da yake yi
sitebabu
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector backup list example.com

Abin da kake gani

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]
HujjaAna buƙataAbin da yake yi
sitebabu

Misali

zinnector backup now example.com

Abin da kake gani

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

zinnector domains

list the domains this key can see

zinnector domains [options]
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector domains

Abin da kake gani

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]

Misali

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>
HujjaAna buƙataAbin da yake yi
domainE to
ZabiAbin da yake yiNa asali
--type <type>only records of this type
--jsonmachine-readable output

Misali

zinnector dns list example.com

Abin da kake gani

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>
HujjaAna buƙataAbin da yake yi
domainE to
typeE to
nameE to
valueE to
ZabiAbin da yake yiNa asali
--ttl <seconds>time to live"3600"
--priority <n>priority, for MX and SRV
--proxiedroute through the CDN
-y, --yesdo not ask

Misali

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

Abin da kake ganithe 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>
HujjaAna buƙataAbin da yake yi
domainE to
recordIdE to
ZabiAbin da yake yiNa asali
-y, --yesdo not ask

Misali

zinnector dns rm example.com rec_7f3a

Abin da kake gani

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

zinnector mail

list mail services

zinnector mail [options]
ZabiAbin da yake yiNa asali
--jsonmachine-readable output

Misali

zinnector mail

Abin da kake gani

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>
HujjaAna buƙataAbin da yake yi
operationE to
ZabiAbin da yake yiNa asali
--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

Misali

zinnector bulk cache_purge --all

Abin da kake ganione 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...>
HujjaAna buƙataAbin da yake yi
question...E to
ZabiAbin da yake yiNa asali
-s, --site <site>ask about a particular site
--no-contextdo not send anything about the local project
--jsonmachine-readable output

Misali

zinnector ai "why is my deploy failing?"

Abin da kake ganiruns 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`.

Ci gaba da karatu

Jagorori a cikin kundin sani

Fara amfani · Ci gaban gida · Ana turawa · Gyara matsala

An gina shi a kan jama'a API

Bayanin API · Me yasa Zinnector®

Sanya shi kuma a kaddamar da wani yanar gizo a cikin minti na gaba

Kyauta, mai lasisi ta MIT, kuma kowane umarni aiki ne da aka rubuta a cikin API na jama'a — babu wani abu a nan da zai iya yin wani abu da API bazai iya ba.

npm install -g zinnector