Lightweight staging packages for LocalWP

Workflow
1

Hi everyone,

The LocalWP team suggested I share this here, so I wanted to ask for feedback from people who regularly build or test WordPress sites locally.

I maintain a free WordPress plugin called StifLi Backup Tools:

https://wordpress.org/plugins/stifli-backup-tools/

It started as a backup / restore / migration plugin, but I’ve recently been improving a workflow that I think may be useful for LocalWP users: lightweight staging / local development packages.

The idea is simple: sometimes a full production clone is too much.

For example, a WooCommerce site may have huge uploads folders, order tables, sessions, logs, transients, and other data that is not always needed for development. In many cases you only need enough of the site to reproduce a bug, test a theme/plugin change, or work locally.

So the new workflow lets you create a more focused LocalWP-friendly package:

  • choose which database tables to include

  • choose which plugins and themes to copy

  • automatically include the active parent theme when using a child theme

  • optionally skip /uploads and map media URLs back to the live site

  • reduce WooCommerce-heavy data and keep only a small order sample

  • strip transient/rewrite/cache noise from the local package

  • export a ZIP with wp-content + database.sql

  • run the export asynchronously with progress, cancel, resume, and stalled-job handling

The goal is not to replace full backups or perfect production clones.

It is more for cases where you want a faster, smaller local dev package instead of moving 20GB+ of media and unnecessary WooCommerce data into LocalWP.

I’d really appreciate feedback from LocalWP users:

Would this kind of lightweight staging/export workflow be useful in your local development process?

And what would you expect before trusting it on larger WooCommerce or client sites?

3 Likes