@smart-cloud/publisher-exporter 1.1.44 → 1.1.45
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -2
- package/dist/content-sync.js +8 -8
- package/dist/crawl.js +6 -6
- package/dist/deploy.js +1 -1
- package/dist/invalidate.js +2 -2
- package/dist/queue-runner.js +3 -3
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @smart-cloud/publisher-exporter
|
|
2
2
|
|
|
3
|
-
`@smart-cloud/publisher-exporter` is the standalone Node.js CLI package behind WP Suite Static Publisher crawl, deploy, invalidate, and queue-runner workflows.
|
|
3
|
+
`@smart-cloud/publisher-exporter` is the standalone Node.js CLI package behind WP Suite Static Publisher crawl, deploy, invalidate, targeted content-sync, and queue-runner workflows.
|
|
4
4
|
|
|
5
5
|
It is designed to run outside WordPress. The WordPress plugin only manages runtime config, queue state, and logs.
|
|
6
6
|
|
|
@@ -111,7 +111,8 @@ When the runtime config contains enabled scheduler rules and the active queue-ru
|
|
|
111
111
|
- Scheduler rules are read from `runtime/config.json` and their last interval buckets are persisted in `runtime/scheduler-state.json`.
|
|
112
112
|
- Scheduler only auto-enqueues jobs into the runtime queue. It does not replace cron, systemd timers, or Windows Task Scheduler.
|
|
113
113
|
- A 1-minute external runner tick is the recommended cadence.
|
|
114
|
-
- Supported scheduled commands are `publish`, `crawl`, `deploy`, `invalidate`, `retry-timeouts`, and `
|
|
114
|
+
- Supported scheduled commands are `publish`, `crawl`, `deploy`, `invalidate`, `retry-timeouts`, `url`, and Professional/Agency-only `content-sync`.
|
|
115
|
+
- Content sync requires a successful normal publish baseline and processes only its configured post types, multisite scope, listings, archives, and sitemap surfaces.
|
|
115
116
|
- The scheduler timezone value is currently informational for operations context; interval matching is based on elapsed minute buckets checked at each queue-runner start.
|
|
116
117
|
- If an equivalent queued or running job already exists for the same command, crawl mode, deployment profile, and URL, that rule is skipped for the current interval bucket.
|
|
117
118
|
|