Forcing function: Easy way to run 10 agents on my site.
- Import the site (Reprint)
forkpress initforkpress clone / forkpress pull
- 10 branches with local previews, separated from each other, fast, versioned, mergable
forkpress serve to start the local server. It exposes all the branches under different subromains (we'll need URL rewrite for <branch-name>.wp.local )git clone <http://wp.local> to clone the repo (or forkpress git clone <http://wp.local> if lacking git CLI tool in the fs)forkpress/git branch create <branch-name> (git checkout -b; git commit; git push could also work -- what's better?)- Separate local directories with different branches of that site
- v1 -- use git worktrees. The agent starts 5 directories with versions of that site, then we do
forkpress commit and that already makes the change previewable via HTTP. Brownie points if we can make it previewable by just changing the working copy without any CLI commands.
- v2 or v3 -- mount from ForkPress to host filesystem using fast COWs
- DB access for the model -- how? SQLite file in the branch? Or MySQL binary protocol? Both? Anything works. For sure we store the data as static files. We also have MySQL WASM at our disposal if needed. We just need to make a choice.
- Publish the site (TBD)
Forcing function: Easy way to run 10 agents on my site.
forkpress initforkpress clone/forkpress pullforkpress serveto start the local server. It exposes all the branches under different subromains (we'll need URL rewrite for<branch-name>.wp.local)git clone<http://wp.local>to clone the repo (orforkpress git clone<http://wp.local>if lacking git CLI tool in the fs)forkpress/git branch create <branch-name>(git checkout -b; git commit; git pushcould also work -- what's better?)forkpress commitand that already makes the change previewable via HTTP. Brownie points if we can make it previewable by just changing the working copy without any CLI commands.