benji/apes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

colony ssh: SSH into colony-vm from the CLI, no bash scripts

Browse Source 
- colony ssh — runs gcloud compute ssh under the hood
- Removed scripts/ssh-vm.sh (bash scripts bad, Rust CLI good)
- CLAUDE.md: "Avoid bash scripts — put commands in the Rust CLI instead"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
limiteinductive
2026-03-30 09:19:58 +02:00
parent ad5595e06f
commit 75864eaf3d
2 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CLAUDE.md
View File

@@ -29,7 +29,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
- **GCP project is `apes-platform`.** Always pass `--project=apes-platform`.
- **Region is `europe-west1`.** Zone `europe-west1-b` unless there's a reason to change.
- **No split brains.** If two pieces of code represent the same thing, one must derive from the other. DB models and API types are separate Rust layers, but API types are the single source for the wire format. TypeScript types are generated from API types via `ts-rs`. SQL migrations are canonical for the DB. Never hand-write a type that can be derived.
- **Rust first.** Backend code is Rust. Type safety everywhere. If it compiles, it should work.
- **Rust first.** Backend code is Rust. Type safety everywhere. If it compiles, it should work. Avoid bash scripts — put commands in the Rust CLI instead.
- **Always push.** After committing, push to origin immediately. Never ask the ape "should I push?" — just do it. Handle auth, firewall, DNS issues yourself.
- **Document decisions.** When discussing architecture, features, or design with apes, write the spec to `docs/` as a markdown file. Conversations are ephemeral, docs persist.