~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

Deploys start the keeper, once its login is on the host

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:deploy/keeper

What changes

deploy.sh starts the keeper. With KNOTLESS_KEEP_REPOS set, it writes /etc/knotless/keep.env from KNOTLESS_KEEP_IDENTIFIER and KNOTLESS_KEEP_PASSWORD (once, from deploy/local.env), adds the keep compose profile once that file is on the host, and passes KNOTLESS_KEEP_REPOS and KNOTLESS_KEEP_ARGS through to the service. Without the login it leaves the keeper out and says so, as it does for the reviewer.

deploy.yml names chadtmiller.com/knotless as the repository it keeps.

deploy/README.md gets a section on the keeper and its row in the service table.

Why

knotless-agent keep and its compose service landed, but nothing in deploy.sh ever set the keep profile or wrote its login. So prod never ran it (COMPOSE_PROFILES=triage,review on the host).

How it was checked

bash -n deploy/deploy.sh. The new block copies the reviewer's line for line, without the Claude login. Until keep.env is on the host, a deploy logs that the keeper is not starting and changes nothing else.

Shortcomings

The keeper still needs its own account, a collaborator of knotless, and its app password written to the host once. A later deploy then starts it.

Changeset: none

🤖 Generated with Claude Code

Approved

This makes deploy.sh start the keeper. It writes keep.env once from KNOTLESS_KEEP_IDENTIFIER and KNOTLESS_KEEP_PASSWORD, adds the keep profile once that file is on the host, and passes KNOTLESS_KEEP_REPOS and KNOTLESS_KEEP_ARGS through to the service. It also sets KNOTLESS_KEEP_REPOS in deploy.yml and adds the README section and table row.

I read the diff and the existing keep service in docker-compose.yml. The keep profile name, the /etc/knotless/keep.env path and the two variable names match what the service reads. The PROFILES handling follows the triage and review blocks, and .env is written the same way. Without the login the deploy only logs that the keeper is not starting, as the body says.

I did not run the script, and I did not check that deploy.yml exports the KNOTLESS_KEEP_IDENTIFIER and KNOTLESS_KEEP_PASSWORD that the first-time write needs. The body expects them in deploy/local.env, so that fits a deploy from your own checkout.

The body carries Changeset: none, and the change touches only deploy files.

Merged as 16abb82