542ed0afe3
Persistent agent memories now live in memory/ in this repo; the Claude auto-memory path is symlinked here so future memories land in the repo and get committed like any other change.
1.2 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| abra-chaos-deploy-checkout-gotcha | abra app new moves the recipe checkout to the release tag — checkout the PR branch AFTER app new, or chaos deploys the wrong tree |
|
On cc-ci, abra app new <recipe> checks out the latest published release tag in
~/.abra/recipes/<recipe>, silently discarding whatever commit you had checked out. A
subsequent abra app deploy --chaos then deploys that tag's tree, not your WIP.
Why: abra pins app creation to the recipe's released version and moves the recipe
checkout to do it; --chaos only means "deploy the working tree as-is at deploy time".
How to apply: in the step-2b direct-deploy loop, order matters: abra app new first,
then git checkout <PR-branch> in the recipe dir, then abra app deploy --chaos.
Verify with the deploy overview (config versions / images) that the intended tree went out.
Also: plausible's .env.sample ships DISABLE_AUTH/DISABLE_REGISTRATION=replace-me, which
crash-loops the app (binary_to_existing_atom("replace-me")) — set them to true/false in
any dev env. See regression-canary-cadence for related CI cadence.