Zinnector® CLI

Çdo komandë, drejtpërdrejt nga --help

Zinnector® 0.1.2 krijon një faqe WordPress në kompjuterin tuaj pa instaluar gjë tjetër veçse Node, e kontrollon atë kundrejt hapësirës së hostimit në të cilën po përgatiteni të vendosni, dhe e dërgon. Kjo faqe gjenerohet nga vetë përkufizimet e komandave të CLI — të njëjtat objekte që shfaq zinnector --help — kështu që nuk mund të jetë në kundërshtim me mjetin që keni instaluar.

36 komanda në Zinnector® 0.1.2.

Instaloje

Një komandë, në Node 24 ose më të re. Falas dhe me licencë MIT; skafodimi dhe ekzekutimi i një faqeje lokalisht nuk kërkojnë asnjë llogari.

npm install -g zinnector

Nyja {node} ose më e re

Ekzekuto node --version; duhet të shfaqë v24 ose më lart. Instalo versionin aktual LTS nga nodejs.org — në Windows, winget install OpenJS.NodeJS.LTS; në macOS, brew install node@24.

Keni parë EBADENGINE?

Ky është npm që ju tregon se Node juaj është më i vjetër se 24. Instalimi përfundon gjithsesi, por CLI refuzon të ekzekutohet dhe e thotë këtë. Përditësoni Node dhe instaloni përsëri.

Në Nyjën 26 ose më të re?

CLI funksionon mirë. Mjedisi ekzekutues WordPress që shkarkon përmban një modul vendor me skedarë binarë të parandërtuar vetëm për Node 24 dhe 25, kështu që gjatë përdorimit të parë Zinnector® shkarkon gjithashtu një Node 24 vetëm për mjedisin ekzekutues — rreth 30 MB, të verifikuar kundrejt shumave kontrolluese të nodejs.org. Asnjë përpilues, asnjë Visual Studio, asgjë për t'u bërë me dorë.

Provojeni se funksionon — dy minuta, pa llogari

Ekzekutoni këto me radhë. Nën secilën prej tyre tregohet se si duket suksesi, kështu që ju e dini momentin kur diçka nuk është në rregull.

  1. Instaloje

    npm install -g zinnector

    Sukses: npm përfundon pa një paralajmërim EBADENGINE.

  2. Kontrollo versionin

    zinnector --version

    Sukses: një numër versioni. Në një version të Node më të vjetër se 24, ai printon një mesazh që thotë se kërkohet Node 24 ose më i ri, dhe del në vend të kësaj.

    0.1.2
  3. Lexoni ndihmën

    zinnector --help

    Sukses: një baner që emërton pesë komandat e rrjedhës, më pas secila komandë me një qëllim në një rresht — lista në këtë faqe.

      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. Krijo strukturën e faqes

    zinnector new my-site

    Sukses: një titull "Created my-site", skedarët që ka shkruar dhe komandat e radhës për t'u ekzekutuar.

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

    cd my-site
    zinnector dev

    Ekzekutimi i parë kërkon vetëm një herë shkarkimin e mjedisit ekzekutiv të WordPress (rreth 570 MB, i ruajtur në memorien cache të vetë Zinnector®). Sukses: një rresht “që ekzekutohet në” me një adresë lokale.

    ✔ running at http://127.0.0.1:9400
      admin: http://127.0.0.1:9400/wp-admin  (already signed in)
  6. Hape atë në një shfletues

    open http://127.0.0.1:9400

    Sukses: një faqe e re WordPress e titulluar “My WordPress Website”, dhe /wp-admin hap panelin e kontrollit tashmë të kyçur. Vendosni një shtojcë në wp-content/plugins dhe ajo do të jetë atje në ringarkimin e ardhshëm.

    Çdo gjë më sipër funksionon pa llogari. Lidhja, kontrolli paraprak dhe dërgimi kërkojnë një çelës API nga paneli juaj i kontrollit dhe një sajt në pritjen web (hosting) të Zinn Digital®.

Rrjedha: krijo, zhvillo, lidh, kontrollo, dërgo

Gjashtë komanda nga asgjëja te një faqe aktive. zinnector new printon këtë listë kur përfundon, kështu që nuk duhet ta mbani mend kurrë.

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

Pika kyçe është e mesmja. Kontrolli i zinnector krahason atë që keni ndërtuar — versionin e PHP, diskun, numrin e skedarëve, versionin e WordPress — me hapësirën ku do të bëni vendosjen, emërton çdo mospërputhje dhe çdo krahasim që nuk mundi ta bëjë, dhe pastaj ju lejon të bëni vendosjen gjithsesi, sepse ju dini gjëra për faqen tuaj që një kontrollues nuk i di.

Referenca e komandave

Të gjitha 36 komandat, në rendin që i liston zinnector --help. Daljet e shënuara si "të kapura" u ngjitën nga një ekzekutim real i këtij versioni; pjesa tjetër tregon formën e saktë që printon komanda, me vlera shembull — domenet, ID-të dhe shifrat tuaja do të ndryshojnë.

Opsione globale, të pranuara para çdo komande:

OpsioniÇfarë bën
-V, --versionprint the version
--profile <name>use a named credential profile
-h, --helpShfaq ndihmën për çdo komandë.

zinnector new

scaffold a WordPress project you can run immediately

zinnector new [options] [name]
ArgumentE detyrueshmeÇfarë bën
namejo
OpsioniÇfarë bënParazgjedhur
-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

Shembull

zinnector new my-site

A shihetcaptured — 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]
OpsioniÇfarë bënParazgjedhur
--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

Shembull

cd my-site
zinnector dev

A shihetcaptured — 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]
OpsioniÇfarë bënParazgjedhur
--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

Shembull

zinnector login

A shihetthe 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]
OpsioniÇfarë bënParazgjedhur
--profile <name>which profile to forget"default"

Shembull

zinnector logout

A shihet

✔ signed out of profile “default”

zinnector whoami

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

zinnector whoami [options]
OpsioniÇfarë bënParazgjedhur
--profile <name>use a named profile
--scopeslist the permissions an API key carries
--jsonmachine-readable output

Shembull

zinnector whoami --scopes

A shihet

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]
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output
--status <status>only sites in this status

Shembull

zinnector sites

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector status example.com

A shihet

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>
ArgumentE detyrueshmeÇfarë bën
sitePo
emailPo
OpsioniÇfarë bënParazgjedhur
--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

Shembull

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

A shihetthe 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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector collaborators example.com

A shihetthe 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>
ArgumentE detyrueshmeÇfarë bën
sitePo
whoPo
OpsioniÇfarë bënParazgjedhur
--yesdo not ask

Shembull

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

A shihetthe 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]

Shembull

zinnector invitations

A shihetthe 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]
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector invitations list

A shihetthe 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>
ArgumentE detyrueshmeÇfarë bën
idPo

Shembull

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

A shihetthe 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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--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

Shembull

zinnector pull

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitePo
dirjo
OpsioniÇfarë bënParazgjedhur
--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

Shembull

zinnector clone client.example.com

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--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

Shembull

zinnector check

A shihetcaptured 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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
-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

Shembull

zinnector push

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--no-waittrigger and exit

Shembull

zinnector deploy example.com

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output
-n, --limit <n>how many to show"10"

Shembull

zinnector deploys example.com

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
versionjo
OpsioniÇfarë bënParazgjedhur
-s, --site <site>site id or domain
--listlist the versions the platform offers
--jsonmachine-readable output

Shembull

zinnector php 8.3 --site example.com

A shihetwith 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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector quota example.com

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector db example.com

A shihetthe 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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--accessonly the access log
--erroronly the error log
--buildthe build log of the most recent deploy instead
--jsonmachine-readable output

Shembull

zinnector logs example.com --error

A shihet--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...>
ArgumentE detyrueshmeÇfarë bën
command...Po
OpsioniÇfarë bënParazgjedhur
-s, --site <site>site id or domain
--commandslist what the platform will run
--jsonmachine-readable output

Shembull

zinnector wp plugin list --site example.com

A shihetthe 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]

Shembull

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]
ArgumentE detyrueshmeÇfarë bën
sitejo
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector backup list example.com

A shihet

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]
ArgumentE detyrueshmeÇfarë bën
sitejo

Shembull

zinnector backup now example.com

A shihet

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

zinnector domains

list the domains this key can see

zinnector domains [options]
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector domains

A shihet

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]

Shembull

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>
ArgumentE detyrueshmeÇfarë bën
domainPo
OpsioniÇfarë bënParazgjedhur
--type <type>only records of this type
--jsonmachine-readable output

Shembull

zinnector dns list example.com

A shihet

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>
ArgumentE detyrueshmeÇfarë bën
domainPo
typePo
namePo
valuePo
OpsioniÇfarë bënParazgjedhur
--ttl <seconds>time to live"3600"
--priority <n>priority, for MX and SRV
--proxiedroute through the CDN
-y, --yesdo not ask

Shembull

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

A shihetthe 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>
ArgumentE detyrueshmeÇfarë bën
domainPo
recordIdPo
OpsioniÇfarë bënParazgjedhur
-y, --yesdo not ask

Shembull

zinnector dns rm example.com rec_7f3a

A shihet

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

zinnector mail

list mail services

zinnector mail [options]
OpsioniÇfarë bënParazgjedhur
--jsonmachine-readable output

Shembull

zinnector mail

A shihet

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>
ArgumentE detyrueshmeÇfarë bën
operationPo
OpsioniÇfarë bënParazgjedhur
--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

Shembull

zinnector bulk cache_purge --all

A shihetone 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...>
ArgumentE detyrueshmeÇfarë bën
question...Po
OpsioniÇfarë bënParazgjedhur
-s, --site <site>ask about a particular site
--no-contextdo not send anything about the local project
--jsonmachine-readable output

Shembull

zinnector ai "why is my deploy failing?"

A shihetruns 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`.

Vazhdo leximin

Udhëzuesit në bazën e njohurive

Fillimi i punës · Zhvillim lokal · Duke u vendosur · Zgjidhja e problemeve

Ndërtuar në API-në publike

Referenca e API-së · Pse Zinnector®

Instalojeni dhe ekzekutoni një faqe në minutën e ardhshme

Falas, me licencë MIT, dhe çdo komandë është një operacion i dokumentuar në API-në publike — asgjë këtu nuk mund të bëjë diçka që API-ja nuk mundet.

npm install -g zinnector