Zinnector® CLI

រាល់ពាក្យបញ្ជា ដោយផ្ទាល់ពី --help

Zinnector® 0.1.3 បង្កើតគេហទំព័រ WordPress នៅលើម៉ាស៊ីនផ្ទាល់ខ្លួនរបស់អ្នក ដោយមិនចាំបាច់ដំឡើងអ្វីផ្សេងក្រៅពី Node នោះទេ វាពិនិត្យមើលធៀបនឹងស្លុតបង្ហោះដែលអ្នករៀបនឹងដាក់ឱ្យប្រើប្រាស់ ហើយបន្ទាប់មកវាធ្វើការជំរុញ (push)។ ទំព័រនេះត្រូវបានបង្កើតឡើងពីនិយមន័យពាក្យបញ្ជាផ្ទាល់របស់ CLI — ដែលជាវត្ថុដូចគ្នាដែល zinnector --help បង្ហាញ — ដូច្នេះវាពុំអាចមានភាពខុសគ្នាពីឧបករណ៍ដែលអ្នកបានដំឡើងនោះឡើយ។

បញ្ជា 36 នៅក្នុង Zinnector® 0.1.3។

ដំឡើងវា

បញ្ជាតែមួយ នៅលើ Node 24 ឬថ្មីជាងនេះ។ ឥតគិតថ្លៃ និងមានអាជ្ញាប័ណ្ណ MIT; ការបង្កើតរចនាសម្ព័ន្ធ និងការដំណើរការគេហទំព័រក្នុងមូលដ្ឋានមិនចាំបាច់មានគណនីអ្វីទាំងអស់។

npm install -g zinnector

Node {node} ឬថ្មីជាងនេះ

ដំណើរការ node --version; វាត្រូវតែបង្ហាញ v24 ឬខ្ពស់ជាងនេះ។ សូមដំឡើង LTS បច្ចុប្បន្នពី nodejs.org — នៅលើ Windows គឺ winget install OpenJS.NodeJS.LTS; នៅលើ macOS គឺ brew install node@24។

ឃើញ EBADENGINE ទេ?

នោះគឺជា npm ដែលប្រាប់អ្នកថា Node របស់អ្នកចាស់ជាង 24។ ការដំឡើងនៅតែត្រូវបន្តរហូតចប់ ប៉ុន្តែ CLI បដិសេធមិនដំណើរការហើយបង្ហាញសារបែបនេះ។ សូមអាប់ដេត Node ហើយដំឡើងម្តងទៀត។

នៅលើ Node 26 ឬថ្មីជាងនេះ?

CLI ដំណើរការបានល្អ។ រ៉ាន់ថាម WordPress ដែលវាទាញយក មានម៉ូឌុលដើមដែលមានប៊ីនែរីបង្កើតទុកជាមុនសម្រាប់ Node 24 និង 25 ប៉ុណ្ណោះ ដូច្នេះនៅពេលប្រើដំបូង Zinnector® ក៏ទាញយក Node 24 សម្រាប់រ៉ាន់ថាមតែមួយមុខដែរ ដែលមានទំហំប្រហែល 30 មេកាបៃ (MB) និងបានផ្ទៀងផ្ទាត់ជាមួយនឹងឆែកសាំ (checksums) របស់ nodejs.org។ គ្មានកម្មវិធីបម្លែងកូដ (compiler) គ្មាន Visual Studio ហើយគ្មានអ្វីដែលត្រូវធ្វើដោយដៃឡើយ។

សាកល្បងមើលថាវាដំណើរការ — ពីរនាទី មិនបាច់បង្កើតគណនី

សូមប្រតិបត្តិការទាំងនេះតាមលំដាប់លំដោយ។ នៅខាងក្រោមចំណុចនីមួយៗគឺជាលទ្ធផលដែលបង្ហាញពីជោគជ័យ ដើម្បីឱ្យលោកអ្នកអាចដឹងបានភ្លាមៗនៅពេលមានបញ្ហាកើតឡើង។

ដំឡើងវា
```
npm install -g zinnector
```
ជោគជ័យ៖ npm បានបញ្ចប់ដោយគ្មានការព្រមាន EBADENGINE ឡើយ។
ពិនិត្យមើលកំណែ
```
zinnector --version
```
ជោគជ័យ៖ លេខកំណែ។ នៅលើ Node ដែលចាស់ជាង 24 វាបង្ហាញសារដែលបញ្ជាក់ថាត្រូវការ Node 24 ឬថ្មីជាងនេះ ហើយជំនួសមកវិញវាចេញពីកម្មវិធី។
```
0.1.3
```
អានជំនួយ
```
zinnector --help
```
ជោគជ័យ៖ បដាដែលរៀបរាប់ឈ្មោះពាក្យបញ្ជាទាំងប្រាំនៃលំហូរ បន្ទាប់មកពាក្យបញ្ជានីមួយៗជាមួយនឹងគោលបំណងមួយជួរ — បញ្ជីនៅលើទំព័រនេះ។
```
  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
  …
```
បង្កើតរគងគេហទំព័រ
```
zinnector new my-site
```
ជោគជ័យ៖ ចំណងជើង “Created my-site” ឯកសារដែលវាបានសរសេរ និងពាក្យបញ្ជាបន្ទាប់ដែលត្រូវដំណើរការ។ គ្មានអ្វីនៅក្នុងនោះជាកន្លែងដាក់ទេ។
```
Created my-site  ·  site
  + zinnector.json
  + wp-content/…
→ run it:
    cd my-site
    zinnector dev
```
ដំណើរការវា
```
cd my-site
zinnector dev
```
ការដំណើរការដំបូងសួរម្តងដើម្បីទាញយកបរិស្ថានពេលរត់ WordPress (ប្រហែល 570 MB ដែលរក្សាទុកក្នុងឃ្លាំងសម្ងាត់ផ្ទាល់ខ្លួនរបស់ Zinnector®)។ ជោគជ័យ៖ បន្ទាត់ “កំពុងដំណើរការនៅ” ជាមួយអាសយដ្ឋានក្នុងមូលដ្ឋាន។
```
✔ running at http://127.0.0.1:9400
  admin: http://127.0.0.1:9400/wp-admin  (already signed in)
```
បើកវាក្នុងកម្មវិធីរុករកបណ្ដាញ
```
open http://127.0.0.1:9400
```
ជោគជ័យ៖ គេហទំព័រ WordPress ថ្មីស្រឡាងមួយដែលត្រូវបានដាក់ចំណងជើងថា “My WordPress Website” ហើយ /wp-admin នឹងបើកផ្ទាំងគ្រប់គ្រងដោយបានចូលប្រើប្រាស់រួចជាស្រេច។ គ្រាន់តែទម្លាក់ plugin មួយចូលទៅក្នុង wp-content/plugins នោះវានឹងបង្ហាញនៅទីនោះពេលផ្ទុកទំព័រឡើងវិញលើកក្រោយ។
អ្វីៗនៅខាងលើដំណើរការដោយមិនចាំបាច់មានគណនីទេ។ តំណភ្ជាប់ ការពិនិត្យជាមុន និងការជំរុញត្រូវការគន្លឹះ API ពីផ្ទាំងគ្រប់គ្រងរបស់អ្នក និងគេហទំព័រមួយនៅលើការបង្ហោះ Zinn Digital®។

លំហូរ៖ បង្កើត, អភិវឌ្ឍ, តភ្ជាប់, ពិនិត្យ, រុញ

ពាក្យបញ្ជាចំនួនប្រាំមួយពីគ្មានអ្វីទៅគេហទំព័រផ្សាយផ្ទាល់។ zinnector new បោះពុម្ពបញ្ជីនេះនៅពេលវាបញ្ចប់ ដូច្នេះអ្នកមិនចាំបាច់ចងចាំវាឡើយ។

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

ចំណុចកណ្តាលគឺចំណុចស្នូល។ ការពិនិត្យរបស់ zinnector ធ្វើការប្រៀបធៀបនូវអ្វីដែលអ្នកបានបង្កើត—កំណែ PHP ថាស ទំហំឯកសារ កំណែ WordPress—ប្រៀបធៀបជាមួយនឹងរន្ធដែលអ្នកត្រៀមដាក់ឱ្យដំណើរការ ដោយដាក់ឈ្មោះរាល់ការមិនស៊ីគ្នា និងរាល់ការប្រៀបធៀបដែលវាមិនអាចធ្វើបាន បន្ទាប់មកអនុញ្ញាតឱ្យអ្នកដាក់ឱ្យដំណើរការដដែល ព្រោះថាអ្នកដឹងរឿងរ៉ាវអំពីគេហទំព័ររបស់អ្នកផ្ទាល់ដែលកម្មវិធីពិនិត្យមិនដឹង។

ឯកសារយោងពាក្យបញ្ជា

ពាក្យបញ្ជាទាំង 36 ទាំងអស់ តាមលំដាប់ដែល zinnector --help រាយពួកវា។ លទ្ធផលដែលបានសម្គាល់ថា "captured" ត្រូវបានបិទភ្ជាប់ពីដំណើរការជាក់ស្តែងនៃកំណែនេះ ចំណែកឯផ្នែកដែលនៅសល់បង្ហាញរូបរាងពិតប្រាកដដែលពាក្យបញ្ជាបោះពុម្ព ជាមួយតម្លៃគំរូ — ដូម៉ែន លេខសម្គាល់ និងតួលេខរបស់អ្នកនឹងមានលក្ខណៈខុសគ្នា។

ជម្រើសសកល ទទួលយកមុនពាក្យបញ្ជាណាមួយ៖

ជម្រើស	មុខងាររបស់វា
`-V, --version`	print the version
`--profile <name>`	use a named credential profile
`-h, --help`	បង្ហាញជំនួយសម្រាប់ពាក្យបញ្ជាណាមួយ។

`zinnector new`

scaffold a WordPress project you can run immediately

zinnector new [options] [name]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`name`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`-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"`
`--here`	scaffold into the current directory instead of a new one

ឧទាហរណ៍

zinnector new my-site

អ្វីដែលអ្នកឃើញ — 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]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--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
`--login`	log in as admin automatically	`true`
`--no-login`	do not log in automatically
`--once`	boot, report what is running, then stop
`--yes`	install the local runtime without asking
`--reset-runtime`	delete the installed runtime and install it again
`-v, --verbose`	show the runtime's own output

ឧទាហរណ៍

cd my-site
zinnector dev

អ្វីដែលអ្នកឃើញ — 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`

zinnector login [options]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--profile <name>`	store under a named profile	`"default"`
`--api <url>`	API base URL	`"https://api.zinndigital.com"`
`--api-key`	paste a per-organisation API key instead of signing in as yourself
`--issuer <url>`	the sign-in service	`"https://auth.zinndigital.com/realms/zinn"`
`--no-browser`	print the sign-in link without trying to open a browser

ឧទាហរណ៍

zinnector login

អ្វីដែលអ្នកឃើញ — 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]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--profile <name>`	which profile to forget	`"default"`

ឧទាហរណ៍

zinnector logout

អ្វីដែលអ្នកឃើញ

✔ signed out of profile “default”

`zinnector whoami`

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

zinnector whoami [options]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--profile <name>`	use a named profile
`--scopes`	list the permissions an API key carries
`--json`	machine-readable output

ឧទាហរណ៍

zinnector whoami --scopes

អ្វីដែលអ្នកឃើញ

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]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output
`--status <status>`	only sites in this status

ឧទាហរណ៍

zinnector sites

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector status example.com

អ្វីដែលអ្នកឃើញ

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>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	បាទ/ចាស
`email`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--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
`--json`	machine-readable output

ឧទាហរណ៍

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

អ្វីដែលអ្នកឃើញ — 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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector collaborators example.com

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>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	បាទ/ចាស
`who`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--yes`	do not ask

ឧទាហរណ៍

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

✔ withdrew the invitation to dev@agency.test

`zinnector invitations`

the invitations waiting for you, and accept one

zinnector invitations [options] [command]

ឧទាហរណ៍

zinnector invitations

អ្វីដែលអ្នកឃើញ — 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]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector invitations 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 accept`

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

zinnector invitations accept [options] <id>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`id`	បាទ/ចាស

ឧទាហរណ៍

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

✔ you now have access to example.com

`zinnector link`

point this project at a hosting slot (and connect its repository)

zinnector link [options] [site]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--repo <owner/name>`	connect this repository to the site on the platform
`--provider <github\|gitlab>`	git provider, when it cannot be inferred
`--branch <name>`	branch a push deploys from
`--no-repo`	only write zinnector.json; do not touch the platform

ឧទាហរណ៍

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

អ្វីដែលអ្នកឃើញ

✔ 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`

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

zinnector pull [options] [site]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--via <seam>`	auto (default), git, or backup	`"auto"`
`--fresh`	take 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"`
`--full`	the whole document root, WordPress core included (default: wp-content only)
`--no-uploads`	leave wp-content/uploads (media) behind
`--live-config`	also write wp-config.php — it holds the LIVE database credentials
`--clean`	empty wp-content before extracting, so deletions on the site are mirrored
`--dry-run`	say what would happen and stop
`--yes`	do not ask

ឧទាហរណ៍

zinnector pull

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	បាទ/ចាស
`dir`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--via <seam>`	auto (default), git, or backup	`"auto"`
`--fresh`	take a new backup rather than using the latest one
`--full`	the whole document root, WordPress core included
`--no-uploads`	leave wp-content/uploads (media) behind
`--live-config`	also write wp-config.php — it holds the LIVE database credentials
`--yes`	do not ask

ឧទាហរណ៍

zinnector clone client.example.com

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--probe`	boot the local runtime and MEASURE its php, rather than trusting zinnector.json
`--all`	show passing checks too
`--strict`	also fail when something could not be checked
`--json`	machine-readable output

ឧទាហរណ៍

zinnector check

អ្វីដែលអ្នកឃើញ — 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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`-f, --force`	deploy even when pre-flight has findings
`--skip-checks`	do not run pre-flight at all
`--probe`	measure the local runtime during pre-flight instead of trusting zinnector.json
`--no-wait`	trigger the deploy and exit without watching it
`--no-git`	do not run git push; deploy whatever the platform already has
`--dry-run`	do everything except the deploy

ឧទាហរណ៍

zinnector push

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--no-wait`	trigger and exit

ឧទាហរណ៍

zinnector deploy example.com

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output
`-n, --limit <n>`	how many to show	`"10"`

ឧទាហរណ៍

zinnector deploys example.com

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`version`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`-s, --site <site>`	site id or domain
`--list`	list the versions the platform offers
`--json`	machine-readable output

ឧទាហរណ៍

zinnector php 8.3 --site example.com

អ្វីដែលអ្នកឃើញ — 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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector quota example.com

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector db example.com

អ្វីដែលអ្នកឃើញ — 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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--access`	only the access log
`--error`	only the error log
`--build`	the build log of the most recent deploy instead
`--json`	machine-readable output

ឧទាហរណ៍

zinnector logs example.com --error

អ្វីដែលអ្នកឃើញ — --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...>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`command...`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`-s, --site <site>`	site id or domain
`--commands`	list what the platform will run
`--json`	machine-readable output

ឧទាហរណ៍

zinnector wp plugin list --site example.com

អ្វីដែលអ្នកឃើញ — 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]

ឧទាហរណ៍

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector backup list example.com

អ្វីដែលអ្នកឃើញ

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]

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`site`	ទេ

ឧទាហរណ៍

zinnector backup now example.com

អ្វីដែលអ្នកឃើញ

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

`zinnector domains`

list the domains this key can see

zinnector domains [options]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector domains

អ្វីដែលអ្នកឃើញ

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]

ឧទាហរណ៍

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>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`domain`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--type <type>`	only records of this type
`--json`	machine-readable output

ឧទាហរណ៍

zinnector dns list example.com

អ្វីដែលអ្នកឃើញ

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>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`domain`	បាទ/ចាស
`type`	បាទ/ចាស
`name`	បាទ/ចាស
`value`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--ttl <seconds>`	time to live	`"3600"`
`--priority <n>`	priority, for MX and SRV
`--proxied`	route through the CDN
`-y, --yes`	do not ask

ឧទាហរណ៍

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

អ្វីដែលអ្នកឃើញ — 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>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`domain`	បាទ/ចាស
`recordId`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`-y, --yes`	do not ask

ឧទាហរណ៍

zinnector dns rm example.com rec_7f3a

អ្វីដែលអ្នកឃើញ

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

`zinnector mail`

list mail services

zinnector mail [options]

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--json`	machine-readable output

ឧទាហរណ៍

zinnector mail

អ្វីដែលអ្នកឃើញ

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>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`operation`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`--all`	every site this key can see
`--site <site...>`	specific sites, by id or domain
`--status <status>`	every site in this status
`-y, --yes`	do not ask
`--json`	machine-readable output

ឧទាហរណ៍

zinnector bulk cache_purge --all

អ្វីដែលអ្នកឃើញ — 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...>

អាគុយម៉ង់	ដែលទាមទារ	មុខងាររបស់វា
`question...`	បាទ/ចាស

ជម្រើស	មុខងាររបស់វា	លំនាំដើម
`-s, --site <site>`	ask about a particular site
`--no-context`	do not send anything about the local project
`--json`	machine-readable output

ឧទាហរណ៍

zinnector ai "why is my deploy failing?"

អ្វីដែលអ្នកឃើញ — 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`.

បន្តអាន

ដំឡើងវាហើយដំណើរការគេហទំព័រមួយក្នុងរយៈពេលមួយនាទីបន្ទាប់

ឥតគិតថ្លៃ មានអាជ្ញាប័ណ្ណ MIT ហើយរាល់ពាក្យបញ្ជាគឺជាប្រតិបត្តិការដែលមានឯកសារយោងក្នុង API សាធារណៈ — គ្មានអ្វីនៅទីនេះដែលអាចធ្វើអ្វីដែល API ធ្វើមិនបាននោះទេ។

npm install -g zinnector

រាល់ពាក្យបញ្ជា ដោយផ្ទាល់ពី --help

ដំឡើងវា

Node {node} ឬថ្មីជាងនេះ

ឃើញ EBADENGINE ទេ?

នៅលើ Node 26 ឬថ្មីជាងនេះ?

សាកល្បងមើលថាវាដំណើរការ — ពីរនាទី មិនបាច់បង្កើតគណនី

លំហូរ៖ បង្កើត, អភិវឌ្ឍ, តភ្ជាប់, ពិនិត្យ, រុញ

ឯកសារយោងពាក្យបញ្ជា

zinnector new

zinnector dev

zinnector login

zinnector logout

zinnector whoami

zinnector sites

zinnector status

zinnector share

zinnector collaborators

zinnector unshare

zinnector invitations

zinnector invitations list

zinnector invitations accept

zinnector link

zinnector pull

zinnector clone

zinnector check

zinnector push

zinnector deploy

zinnector deploys

zinnector php

zinnector quota

zinnector db

zinnector logs

zinnector wp

zinnector backup

zinnector backup list

zinnector backup now

zinnector domains

zinnector dns

zinnector dns list

zinnector dns add

zinnector dns rm

zinnector mail

zinnector bulk

zinnector ai

បន្តអាន

មគ្គុទ្ទេសក៍នៅក្នុងមូលដ្ឋានចំណេះដឹង

កញ្ចប់ និងប្រភពរបស់វា

សាងសង់ឡើងនៅលើ API សាធារណៈ

ដំឡើងវាហើយដំណើរការគេហទំព័រមួយក្នុងរយៈពេលមួយនាទីបន្ទាប់

`zinnector new`

`zinnector dev`

`zinnector login`

`zinnector logout`

`zinnector whoami`

`zinnector sites`

`zinnector status`

`zinnector share`

`zinnector collaborators`

`zinnector unshare`

`zinnector invitations`

`zinnector invitations list`

`zinnector invitations accept`

`zinnector link`

`zinnector pull`

`zinnector clone`

`zinnector check`

`zinnector push`

`zinnector deploy`

`zinnector deploys`

`zinnector php`

`zinnector quota`

`zinnector db`

`zinnector logs`

`zinnector wp`

`zinnector backup`

`zinnector backup list`

`zinnector backup now`

`zinnector domains`

`zinnector dns`

`zinnector dns list`

`zinnector dns add`

`zinnector dns rm`

`zinnector mail`

`zinnector bulk`

`zinnector ai`