Title: SpawnWP Deploy Author: wpvoicer Published: 2026 年 7 月 20 日 Last modified: 2026 年 7 月 20 日 --- 搜尋外掛 ![](https://ps.w.org/spawnwp-deploy/assets/banner-772x250.png?rev=3614476) ![](https://ps.w.org/spawnwp-deploy/assets/icon.svg?rev=3614476) # SpawnWP Deploy 由 [wpvoicer](https://profiles.wordpress.org/wpvoicer/) 開發 [下載](https://downloads.wordpress.org/plugin/spawnwp-deploy.0.3.4.zip) * [詳細資料](https://tw.wordpress.org/plugins/spawnwp-deploy/#description) * [使用者評論](https://tw.wordpress.org/plugins/spawnwp-deploy/#reviews) * [安裝方式](https://tw.wordpress.org/plugins/spawnwp-deploy/#installation) * [開發資訊](https://tw.wordpress.org/plugins/spawnwp-deploy/#developers) [技術支援](https://wordpress.org/support/plugin/spawnwp-deploy/) ## 外掛說明 SpawnWP Deploy provides two administrator-initiated workflows: * Capture a configured WordPress site as a reusable blueprint on a self-hosted SpawnWP server. * Publish a finished site once to a separate, fresh WordPress installation. It is not a continuous staging or synchronization system. Site-to-site deployment is limited to an empty destination and keeps rollback data for seven days. Connections use single-use pairing codes, signed requests and replay protection. For blueprint capture, the administrator chooses whether to include plugins, themes, uploads and database content. WordPress users and user metadata are excluded. The source site URL is replaced with a fixed placeholder in captured database content, and each site created from the blueprint receives its own administrator credentials. #### Requirements * WordPress single-site. * PHP 7.4 or later with the Sodium and ZIP extensions. * HTTPS with a publicly trusted certificate on paired endpoints. * A reachable WordPress REST API without an additional HTTP password. * Write access to the WordPress plugin, theme and uploads directories. * Sufficient free disk space for staging and rollback data. Always back up important sites before using deployment or capture tools. ### External Connections This plugin does not contact a SpawnWP-operated SaaS platform and does not send telemetry to SpawnWP merely because it is installed, activated or loaded. An administrator can explicitly pair the plugin with either: 1. another WordPress site running SpawnWP Deploy; or 2. a self-hosted SpawnWP server whose URL is supplied by the administrator. During a requested deployment or capture, the plugin sends the selected package and technical metadata to that administrator-selected endpoint. Depending on the selected options, this can include plugin and theme files, media uploads, database content, WordPress and PHP versions, plugin names and versions, package checksums, job identifiers and connection signatures. WordPress user and user-meta tables are excluded. The remote endpoint is operated by the site administrator or their chosen provider. Its privacy and retention practices are therefore controlled by that operator. SpawnWP is self-hosted open-source software distributed under the MIT License: * SpawnWP project: https://spawnwp.com/ * Source code and license: https://github.com/tts-empire/spawnwp * Security documentation: https://spawnwp.com/docs/security/ * Optional SpawnWP platform telemetry notice: https://spawnwp.com/privacy/telemetry/ When the plugin inventory is displayed and WordPress does not already have cached update information for an active plugin, SpawnWP Deploy may query the WordPress. org Plugins API using WordPress core’s `plugins_api()` function. It sends the plugin slug and uses the response only to classify the plugin as WordPress.org-hosted or custom. The result is cached for one day. WordPress.org privacy policy: https:// wordpress.org/about/privacy/ ## 螢幕擷圖 [⌊Create a reusable blueprint from a configured WordPress site.⌉⌊Create a reusable blueprint from a configured WordPress site.⌉[ Create a reusable blueprint from a configured WordPress site. [⌊Review connected SpawnWP servers and licensed or custom plugin warnings.⌉⌊Review connected SpawnWP servers and licensed or custom plugin warnings.⌉[ Review connected SpawnWP servers and licensed or custom plugin warnings. [⌊Publish a finished site to a paired empty WordPress destination.⌉⌊Publish a finished site to a paired empty WordPress destination.⌉[ Publish a finished site to a paired empty WordPress destination. [⌊Generate a short-lived connection key on an eligible destination.⌉⌊Generate a short-lived connection key on an eligible destination.⌉[ Generate a short-lived connection key on an eligible destination. ## 安裝方式 1. Install and activate SpawnWP Deploy. 2. Open Tools > SpawnWP Deploy. 3. Choose the workflow that applies to the current site. 4. Generate or paste the single-use pairing code at the administrator’s request. 5. Review the selected content and confirmations before starting the operation. ## 常見問題集 ### Does this continuously synchronize two sites? No. It performs a one-time publish to an empty destination. It does not merge later changes, orders, comments, form submissions or users. ### Is a SpawnWP server required? Only for reusable blueprint capture. A one-time site-to-site publish uses SpawnWP Deploy on both WordPress installations. ### Does the plugin send data automatically? No deployment or capture payload is sent automatically. An administrator must pair an endpoint and explicitly start the operation. A cached WordPress.org plugin-information lookup may occur when an administrator opens the blueprint inventory, as documented in External Connections. ### Are WordPress users copied? No. User and user-meta tables are excluded. On deployment, ownership of imported content is assigned to the administrator of the destination site. ### Can I deploy over an existing site? No. The destination guard rejects sites containing application content or unexpected active plugins. Use a dedicated backup or migration product when merging into an active site. ### Where is temporary data stored? Packages and receiver workspaces are stored below the WordPress uploads directory in spawnwp-deploy/, protected from direct web access, and removed after completion or expiry. Rollback data is retained for up to seven days. ## 使用者評論 這個外掛目前沒有任何使用者評論。 ## 參與者及開發者 以下人員參與了開源軟體〈SpawnWP Deploy〉的開發相關工作。 參與者 * [ wpvoicer ](https://profiles.wordpress.org/wpvoicer/) [將〈SpawnWP Deploy〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/spawnwp-deploy) ### 對開發相關資訊感興趣？ 任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/spawnwp-deploy/)、 查看 [SVN 存放庫](https://plugins.svn.wordpress.org/spawnwp-deploy/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/spawnwp-deploy/?limit=100&mode=stop_on_copy&format=rss) 訂閱[開發記錄](https://plugins.trac.wordpress.org/log/spawnwp-deploy/)。 ## 變更記錄 #### 0.3.4 * Added remembered blueprint capture fields and safe patch-version suggestions. * Added a clear reset flow for starting a different blueprint. * Prepared the plugin for WordPress.org distribution and validation. ## 中繼資料 * 版本 **0.3.4** * 最後更新 **1 週前** * 啟用安裝數 **少於 10 次** * WordPress 版本需求 ** 6.8 或更新版本 ** * 已測試相容的 WordPress 版本 **7.0.2** * PHP 版本需求 ** 7.4 或更新版本 ** * 語言 * [English (US)](https://wordpress.org/plugins/spawnwp-deploy/) * 標籤: * [blueprint](https://tw.wordpress.org/plugins/tags/blueprint/)[deployment](https://tw.wordpress.org/plugins/tags/deployment/) [development](https://tw.wordpress.org/plugins/tags/development/)[migration](https://tw.wordpress.org/plugins/tags/migration/) [staging](https://tw.wordpress.org/plugins/tags/staging/) * [進階檢視](https://tw.wordpress.org/plugins/spawnwp-deploy/advanced/) ## 評分 這個項目尚無任何評論記錄。 [Your review](https://wordpress.org/support/plugin/spawnwp-deploy/reviews/#new-post) [查看全部使用者評論](https://wordpress.org/support/plugin/spawnwp-deploy/reviews/) ## 參與者 * [ wpvoicer ](https://profiles.wordpress.org/wpvoicer/) ## 技術支援 使用者可在技術支援論壇提出意見反應或使用問題。 [檢視技術支援論壇](https://wordpress.org/support/plugin/spawnwp-deploy/)