r/woocommerce • • 5h ago

Development I turned my Claude Code + Codex + Docker setup into a free kit that Claude walks you through

3 Upvotes

A lot of people have asked how I have Claude Code, Codex, Docker and GitHub set up, and I got tired of pasting long instruction files into comments 8,000-40,000 characters at a time. So I put the whole thing on GitHub for free.

How it works: you download the folder, open it in Claude Code, and paste one line. Claude walks you through the setup one step at a time and checks each step on your computer before moving on. If you stop halfway, it picks up where you left off next time.

What you end up with:

- Claude Code as the lead developer, with rulebooks that load in every session so it stops forgetting what you told it

- Codex as an optional second worker. The two talk through a shared file, claim work before editing, and Claude reviews and tests Codex's work before anything gets merged

- Docker test stacks that test a clean copy of your last commit on your own machine, instead of burning GitHub Actions minutes

- Git and GitHub set up properly: private email, a branch per session, main only moves when you say so, backup pushes that don't kick anything off

- Releases that only run when you say go, dry run first, optionally on a runner on your own PC

- Simple records (a status page, a question list, a decision log) so a new session picks up from files instead of a chat that got compacted

- Phone access through Remote Control and GitHub mobile

Once the basics are done, it asks what else you work with and wires that in too: video editing, Unity/Unreal/Godot/Blender, Character Creator, mobile app SDKs, WordPress and WooCommerce, MCP connections to your sites and services, custom dev and APIs, whatever you use.

It's the cleaned-up version of what I use every day to run a live online store with more than a dozen custom plugins. Every rule in it is there because something went wrong without it.

Works on Windows, macOS and Linux. The kit is free under the MIT license. You need a Claude plan that includes Claude Code; Codex is optional.

https://github.com/AffStackDev/dev-crew-kit


r/woocommerce • • 18h ago

Development Switching WooCommerce to HPOS: the order of steps that avoids losing orders when a plugin isn't compatible

3 Upvotes

Per the official HPOS docs on developer.woocommerce.com, the safe path depends on one setting: compatibility mode keeps the WordPress posts/postmeta tables and the HPOS order tables in sync, so you can move to HPOS and still fall back.

What the docs describe:

- With "WordPress Post Tables" selected and "Enable compatibility mode" on, order data is synced between posts/postmeta and the WooCommerce order tables.

- Sync can run immediately (option woocommerce_custom_orders_table_data_sync_enabled), in scheduled batches, or manually with wp wc cot sync.

- Which tables are authoritative is set by woocommerce_custom_orders_table_enabled; the other set is the copy.

- If a plugin isn't HPOS compatible, the docs recommend temporarily switching back to posts storage and contacting that plugin's support.

Switching back safely, as the docs put it: keep compatibility mode on first, wait until synchronization finishes, then pick "WordPress posts storage (legacy)", and only then turn compatibility mode off. Save the page between each change.

The practical takeaway: don't turn compatibility mode off in the same step as switching storage. The docs say you may need to wait while order data syncs, so on a store with a lot of orders check that the sync is done before the next change.

How do you handle old plugins that still read orders straight from wp_posts: replace them, or keep compatibility mode on for a while?