Linux 软件免费装
Banner图

StaticPush by Quintaphon

开发者 quintaphon
更新时间 2026年11月15日 03:00
捐献地址: 去捐款
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

github cloudflare jamstack static site static site generator

下载

2.16.8

详情介绍:

StaticPush by Quintaphon is a static site generator for WordPress. It exports your WordPress site to plain HTML and publishes it to GitHub (for Cloudflare Pages or any Git-based host), straight to Cloudflare Pages, or as a ZIP. After the first full push, every change you make in WordPress is pushed automatically, and only the pages that changed are sent. Your visitors get a static site: fast, cheap to host and with nothing to hack. You keep editing in WordPress as usual. Plugin site: quintaphon.com/wordpress/staticpush Documentation: quintaphon.com/docs/wordpress/staticpush Publish Export Features for the static site Media Offload Mirror your media library to a Cloudflare R2 bucket over the S3 API: resumable background sync with parallel uploads, pause and resume, automatic upload of new media, skip rules for sizes you don't need, and media links in exported pages pointed at your media domain. Image sizes kept out of R2 are replaced by the original in exported pages, so no image breaks. Monitor

安装:

  1. Install StaticPush by Quintaphon from Plugins > Add New (or upload the zip) and activate it.
  2. Go to Static Push > Destination, choose GitHub and click Connect GitHub. Enter the code shown on github.com and approve.
  3. Pick a repository, or click New to create a private one.
  4. Go to Export > Link rewriting, choose Full address and enter your public site address (for example https://www.example.com). Save.
  5. Click Push > Full site.
  6. In Cloudflare: Workers & Pages > Create > Pages > Connect to Git, pick the repository. Framework preset: None, build command: empty, output directory: /.
From now on every change in WordPress becomes a commit, and Cloudflare Pages publishes it. Recommended: move WordPress to its own hostname (for example wp.example.com), point your public domain at the static host, and turn on Stealth > Private WordPress. Media on Cloudflare R2 (optional): create a bucket and an R2 API token with Object Read & Write, enter them under Media Offload, click Test connection, then Sync media library now. Connect your media domain to the bucket (R2 > bucket > Settings > Custom Domains) and run a full push. Keys can also live in wp-config.php instead of the database: define( 'CFSP_GITHUB_TOKEN', 'github_pat_...' ); // fine-grained token for one repository define( 'CFSP_API_TOKEN', '...' ); // Cloudflare Pages Direct Upload define( 'CFSP_ACCOUNT_ID', '...' ); define( 'CFSP_R2_ACCESS_KEY', '...' ); // Media Offload define( 'CFSP_R2_SECRET_KEY', '...' ); define( 'CFSP_BASIC_AUTH', 'user:password' ); // if WordPress is behind HTTP basic auth

屏幕截图:

  • Destination: connect GitHub and pick a repository.
  • Export settings: link rewriting and page discovery.
  • Health Check.
  • Media Offload to Cloudflare R2.
  • Site Search on the static site.

升级注意事项:

2.16.3 License change only: StaticPush is now GPLv2 or later and ready for the WordPress.org plugin directory. 2.16.2 Feeds and sitemaps drop XSLT, which browsers are removing, and use a small script for the browser view instead. Run one Full site push after updating. 2.15.9 Adds an optional page limit for listing pages on automatic pushes. Nothing changes until you set it. 2.15.7 Wildcard lines in your _redirects box no longer switch off other redirects. Push once after updating to deploy the corrected file. 2.15.6 Fixes blank pages on servers where a clean-up pattern hit PCRE limits, and never publishes an empty or cut-off page again. Run one "Full site" push after updating if your last export came out blank. 2.15.5 The Related Posts headline now also applies to Jetpack's box, and full exports of large sites are faster. Run one "Full site" push after updating. 2.15.4 Posts split into several pages now update every page on push. Run one "Full site" push after updating. 2.14.9 First public release.

常见问题:

Do I need to keep WordPress running?

Yes. You keep writing and editing in WordPress; Static Push turns the result into a static site. Visitors only ever see the static copy, so WordPress can live on a private hostname.

How long does a full push take?

It depends on the number of addresses (posts, category and tag pages, pagination, feeds, files) and on how fast WordPress builds a page. A site with a few thousand addresses usually takes 10 to 20 minutes. After that, automatic pushes only export the pages that changed.

Will comments, contact forms and search work?

Search works through the built-in static search. Forms can be sent to an external form service. WordPress comments need WordPress, so remove the comment form or use an external comments service.

My scheduled posts are published late.

WP-Cron only runs when someone visits WordPress. Keep Automation > Publish missed scheduled posts on, and have a service such as cron-job.org call the wp-cron.php address shown on that page every minute.

What happens to my data if I delete the plugin?

By default, settings, the GitHub connection, media records and exported files are kept, so reinstalling picks up where you left off. Turn on Tools > Delete all data when the plugin is deleted first if you want everything removed. Your static site, GitHub repository and R2 bucket are never touched.

Does it work with page caches?

Yes. Exports bypass page caches with a query parameter and a no-cache header.

更新日志:

2.16.8 2.16.7 2.16.5 2.16.4 2.16.3 2.16.2 2.15.10 2.15.9 2.15.8 2.15.7 2.15.6 2.15.5 2.15.4 2.14.9