Linux 软件免费装
Banner图

Glaciate - Static Site Publisher

开发者 brianmaloney
更新时间 2026年11月21日 10:20
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

performance security export static site static html

下载

2.0.4 2.0.2 2.0.3

详情介绍:

Glaciate turns your WordPress site into plain HTML, CSS and images that any web host can serve, without PHP or a database. You keep writing in WordPress; visitors get a static copy that is fast, cheap to host and hard to break. Links, images, srcset, stylesheets, scripts, structured data, feeds and sitemaps are all rewritten to your public address. A 404 page, a _redirects file and a _headers file (so feeds keep their type on Netlify and Cloudflare) are generated for you. For developers Every stage has actions and filters (list of hooks), and deploy targets are pluggable through a small interface. All features are available from WP-CLI: wp glaciate build, status, why, deploy, zip, settings, target, secret, schedule, forms, doctor and more.

安装:

  1. Install and activate the plugin.
  2. Go to Static Site in the admin menu.
  3. Choose where the static site should go and click Publish my site.
Your site needs pretty permalinks (anything but "Plain" under Settings → Permalinks). If your server can't reach its own address (common behind proxies and in containers), set define( 'GLACIATE_CONNECT_TO', '127.0.0.1:80' ); in wp-config.php to an address that reaches the web server.

常见问题:

Do I need to pay for anything?

No. Every feature is free and stays free.

Does the plugin send data anywhere?

No. It makes requests to your own site, to render pages, and to the deploy target you configure (for example your S3 bucket or Netlify site), to publish. Nothing else, and nothing until you set a target up.

How are deploy credentials stored?

Encrypted in the database, with a key derived from the security keys in wp-config.php, and never displayed again. You can also set any of them with a constant or an environment variable (for example GLACIATE_S3_SECRET_ACCESS_KEY) so they are never stored at all. If the security keys change, saved credentials can no longer be read; Site Health says which ones to enter again.

Can it replace files that aren't its own?

No. On a folder, SFTP server or S3 bucket it only deletes files it published there itself, and a folder must be empty or marked as its own first. A Git branch or Cloudflare Worker that already has content from elsewhere is refused unless you allow replacing it.

Does search work on the static site?

Yes. Glaciate publishes a search index with your site, and your theme's search forms open a results window that searches it in the browser. Results include every published page (title and text from the page itself), and the index is updated along with the pages that change. You can turn it off under Settings → Search.

Can I use Pagefind instead?

Yes, if your host builds the site: a GitHub Actions workflow on the Git target, Netlify or Cloudflare Pages. Add npx pagefind --site . to that build and choose "Pagefind, run by your host's build step" under Settings → Search. Glaciate doesn't include or run Pagefind, because it is a separate program. Your search forms keep the same results window. Themes can choose what is searchable by marking elements with data-glaciate-search, or leave parts out with data-glaciate-search-ignore.

Do forms and comments work on the static site?

Yes, once you turn on Forms under Settings → Forms. A static host can't run them, so Glaciate points them at a receiver:

  • This site, if your WordPress site is reachable from the internet at its own address. Nothing else to install.
  • A receiver you run elsewhere, if WordPress is private. Download it from the settings screen (or wp glaciate forms receiver php|cloudflare|netlify): a single PHP file for any PHP host, a Cloudflare Worker or a Netlify Function. It checks each submission and forwards it to your site, signed with a secret you set on both sides. It can also send submissions to a webhook, or (the PHP file) by email, without WordPress.
Contact Form 7, WPForms, Gravity Forms and the comment form are recognized automatically, and each submission is handled by that plugin as if it had been sent on your site: its validation, emails and stored entries work as usual. Other forms work if your theme marks them with data-glaciate-form="name"; their submissions are emailed to you. File uploads aren't supported.

How are forms protected from spam?

Every form gets a hidden field that people don't see and bots fill in, the time the page was open is checked (bots are quicker than people), each visitor can send five forms in ten minutes, and submissions must come from your static site. For more protection choose Cloudflare Turnstile or hCaptcha; these are outside services, so they are off unless you pick one.

Which pages are left out?

Drafts, private posts and password-protected posts are never published. You can leave out more addresses in Settings.

更新日志:

2.0.4 2.0.3 2.0.2 2.0.1 2.0.0 1.1.1 1.1.0 1.0.3 1.0.2 1.0.1 1.0.0 0.4.0 0.3.0 0.2.0 0.1.0