openpouch 0.2.1 → 0.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -0
- package/openpouch.js +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,6 +10,13 @@ npx openpouch deploy
|
|
|
10
10
|
|
|
11
11
|
You get a live `https://<slug>.openpouch.sh` URL plus a claim link. The agent deploys autonomously; a human claims it via the link to keep it. openpouch writes the deployment truth (`deploy.manifest.json`, `deploy.evidence.json`, `DEPLOYMENT.md`) back into your repo, so any agent can resume after context loss.
|
|
12
12
|
|
|
13
|
+
> **Framework frontends (React/Vite/Next/Svelte…): deploy the _built output_, not the source folder.** `openpouch deploy` ships whatever folder you run it in, as-is. So build first, then deploy the build directory:
|
|
14
|
+
> ```bash
|
|
15
|
+
> npm run build
|
|
16
|
+
> cd dist && npx openpouch deploy # Vite → dist/ · CRA → build/ · Next static export → out/
|
|
17
|
+
> ```
|
|
18
|
+
> A raw, unbuilt source folder is served as static files (the app won't run). Server-side build-on-deploy is on the roadmap.
|
|
19
|
+
|
|
13
20
|
## Accounts (optional)
|
|
14
21
|
|
|
15
22
|
Start anonymous, or create a free account for higher limits — entirely from the agent, no dashboard:
|
package/openpouch.js
CHANGED
|
@@ -5363,6 +5363,7 @@ function renderAgentsSection(projectName) {
|
|
|
5363
5363
|
"",
|
|
5364
5364
|
`${projectName} deploys via openpouch \u2014 an agent-native deployment control plane. This works the same from any agent harness.`,
|
|
5365
5365
|
"",
|
|
5366
|
+
"- **Framework frontends (React/Vite/Next/Svelte\u2026): deploy the _built output_, not the source folder.** `openpouch deploy` ships whatever directory you run it in, as-is \u2014 so build first, then deploy the build directory: `npm run build`, then `cd dist && openpouch deploy` (Vite\u2192`dist/`, CRA\u2192`build/`, Next static export\u2192`out/`). A raw, unbuilt source folder is served as static files (the app won't run); server-side build-on-deploy is on the roadmap.",
|
|
5366
5367
|
"- **Deployment truth** (what is live, where, which commit, rollback anchor): read `DEPLOYMENT.md` or `deploy.evidence.json`. Config lives in `deploy.manifest.json`, agent permissions in `deploy.policy.json`.",
|
|
5367
5368
|
"- **CLI:** `openpouch inspect` \xB7 `plan` \xB7 `preview` (autonomous if policy allows) \xB7 `prod` \xB7 `verify` \xB7 `logs` \xB7 `rollback`. Add `--json` for a single machine-readable JSON object; errors come as `{category, message, fix}` \u2014 act on the fix. Exit codes are documented API.",
|
|
5368
5369
|
"- **Relay the `summary` to your human:** every result (CLI `--json` and MCP) carries a top-level `summary` \u2014 plain-language, jargon-free text written for a non-technical operator. Pass it on verbatim: it says what happened, whether the app is live and healthy, the live link, and what (if anything) the human needs to do. The **live URL is the primary result** \u2014 on a successful deploy it's the top-level `url` field, ready to share.",
|
package/package.json
CHANGED