oficina / memoria Public

docs: the deploy section named a binary no build produces

Two things it got wrong, both found by following it:

- `./releases/memoria-arm64`. The Makefile writes
  `releases/memoria-linux-arm64` — the binary is named for its target, and
  `make release` prints the correct command on the way out. Trust that
  over the README.
- It still opened with "Not done — this has never run anywhere but
  localhost", which stopped being true before the previous commit.

Also records that `carlos deploy` counts untracked files when it decides
the tree is unclean. An editor directory or a stray dotfile is enough to
refuse the deploy, and the message talks about the version defaulting to
the git sha, which does not obviously point at untracked noise. The fix is
to pass the sha make release stamped, not to commit the noise.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YJRwhRTr2kBeBjQNuH4HWm

Paul Campbell pushed by paul@keymail.dev 1 month ago 1b68ced353652f0b203929b0ad5601cbabb1ce8a parent cf77e8e

1 file changed, +13 −4

README.md +13 −4

diff --git a/README.md b/README.md

index 9780666..e933a85 100644

--- a/README.md

+++ b/README.md

@@ -120,14 +120,23 @@ of refusing loudly.

## Deploying

-Not done — this has never run anywhere but localhost. When you want it on

-the estate:

```

make release

-carlos deploy --app memoria --account bds --channel edge --timeout 5m ./releases/memoria-arm64

+carlos deploy --app memoria --account bds --channel edge --timeout 5m releases/memoria-linux-arm64

```

+Trust the command `make release` prints over the one written here: it

+names the path it actually built. This section used to say

+`./releases/memoria-arm64`, which no build has ever produced — the binary

+is named for its target, `linux-arm64`.

+`carlos deploy` refuses to run when the tree is unclean, and it counts

+untracked files. A stray editor directory or dotfile in the checkout is

+enough to stop it, with a message about the version defaulting to the git

+sha. When the tracked tree is genuinely clean, pass the sha `make release`

+stamped — `--version $(git rev-parse --short HEAD)` — rather than

+committing noise to get past it.

Flags go **before** the binary path; Go's flag package stops parsing at

the first non-flag argument, so a path first makes `--account` invisible.

`carlos deploy`, never `carlos ship` on its own. Then poll