Linux 软件免费装
Banner图

DeploySeal

开发者 deployseal
更新时间 2026年11月9日 17:29
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: MIT
版权网址: 版权信息

标签

woocommerce testing release qa uat

下载

详情介绍:

Test releases on your real site, and prove what was tested. DeploySeal lets your team and stakeholders review a WordPress or WooCommerce site before it goes live: testers follow a checklist on the actual pages, pin issues where they see them (screenshot, session replay and browser details captured automatically), developers fix and send them back for verification, and the people who sign off do so on a record that cannot be quietly changed afterwards. This plugin is the WordPress install path for that widget. It does what a pasted script tag cannot: Setup takes two fields. Create an environment for the site in DeploySeal, paste its public key into Settings → DeploySeal, tick Enabled, save. The page then shows exactly what the site will send (origins to register, declared environment label, the build marker, the rendered tag) so you can confirm it matches. Everything else (environment label, build marker source, git SHA file, inventory) lives under Advanced and Platform inventory with sensible defaults. What it sends. Only the widget tag and, if you enable it, the platform inventory. Visitor and customer data is never touched; the widget loads for everyone but only activates for invited testers on registered origins. Requires a DeploySeal account. DeploySeal is currently in private pilot: request access at deployseal.com. The plugin is open source under MIT; issues and pull requests are welcome on GitHub. Documentation: deployseal.com/docs/wordpress. External services This plugin connects to DeploySeal, a hosted go-live sign-off service operated at deployseal.com. DeploySeal terms of service and privacy policy.

安装:

  1. Install through Plugins → Add New (search for "DeploySeal"), or upload deployseal-1.0.0.zip from the GitHub releases through Plugins → Add New → Upload Plugin, then Activate.
  2. In DeploySeal, open your site and create an environment for this WordPress site (for example Staging or Production). Register the origin(s) shown on Settings → DeploySeal under "What this site will send".
  3. Copy the environment's public key (it starts with ls_) into Site key, tick Enabled, Save.
  4. Open the site once; the environment shows as Live in DeploySeal. If you had pasted a DeploySeal snippet into the theme or a header plugin, remove it: DeploySeal warns when two install paths are live on one environment.
On a multisite network, network-activate the plugin or activate it per site; each site then gets its own Settings → DeploySeal page and its own environment key.

屏幕截图:

  • Platform inventory. With a DeploySeal API key the plugin reports the installed plugins and themes, at which versions, every six hours or on demand.

常见问题:

Does it slow my site?

No measurable amount. The plugin adds one async script tag to <head>: the browser downloads the 1 KB loader in parallel without blocking rendering, and the rest of the widget only loads after that. For visitors who are not invited testers the widget stays dormant. On the server, the plugin reads one option per request (and your SHA file, if you configured one). Nothing is added to wp-admin unless you turn that on.

What does it send?

The browser sends a heartbeat per page load (site key, scrubbed page URL, page title, environment label, build marker, widget version and installer) so DeploySeal can show the environment as Live. Invited testers also send the issues they pin, with screenshot and session replay. Only if you add an API key does the server send the platform inventory: installed plugins and themes with their versions, the WordPress and PHP versions and the build marker. No settings, users, customers or orders ever leave the site. See "External services" above.

Does it work with WooCommerce?

Yes. There is nothing WooCommerce-specific to configure: the tag loads on shop, cart and checkout pages like any other page, the plugin declares compatibility with High-Performance Order Storage and the cart and checkout blocks, and the platform inventory records the WooCommerce version and its extensions.

Which build marker will it send?

By default: the DEPLOYSEAL_BUILD constant when wp-config.php defines one; otherwise the WordPress version plus the active theme and its version (7.1.2+twentytwentyfive-1.3), plus the short git SHA when a SHA file your deploy writes can be read (7.1.2+twentytwentyfive-1.3+a1b2c3d). The settings page prints the exact value; copy it verbatim into the campaign's release identifier.

Why does DeploySeal say the environment is Not seen?

Most often the origin: DeploySeal matches scheme://host[:port] exactly, so register every origin the settings page lists. Also check that Enabled is ticked, that the key is the one for this environment, and that a caching plugin has been purged since you enabled the plugin.

Is the site key a secret?

No. It only works from the environment's registered origins, which is why it can sit in your HTML. The API key used for the platform inventory is a secret: the settings page never shows it again once saved.

更新日志:

1.0.1 1.0.0