git clone https://peat.eth.demokluster.com/peat0.git
# yes we're doing git (readonly) over ipfs :)

道法自然 — vibes/patterns/philosophies
├─ 德     entrypoint-oriented development
├─ 陰陽   sliceable monorepo > repo-per-microservice  
├─ 無為   all changes thru reusable idempotent scripts
├─ 柔     strangler vine development
├─ 自然   tighten the loop (aka fuck Jenkins)
├─ 水     💧 opensource/generic > lock-in (k8s > vercel, kimi&glm > claude&"open"ai)
├─ 樸     🌱
└─ 無名   535🍉🕯️

Hello internet neighbor!

My name is pete, this is my digital garden, I'd like to share it with you

• it's a forkable/POC rails-inspired js monorepo (with ts dustings) I initially built for deploying/self-hosting my (next)js apps & related infra/services to k8s

  • specifically to docker/kaniko build & kubectl apply a js entrypoint of itself & its importtree incl nec Deployment Secrets Svc Ingress ConfigMap postgres(cnpg or vanilla postgres dockerimage) etc
  • only re-runs docker build when entrypoint importtree changes (docker image name is deterministic from the git sha filtered to files in ep's importtree + hash(generated dockerfileContent))
  • uses AST analysis to impl many useful things like
    • <ep> diff
    • <ep> howimports <path>
    • ptm mv <pt0/serverF/whateverF.mjs> <pt0/sharedF/whatevsF.mjs> mv's & updates all refs across monorepo
    • ptm bisect "pt0/deployF/testsF/epPtTestsF.mts runtests" --good=4999803345 bisects in a worktree
  • many eps impl <ep> runtests which saves result to --history for^ & knowing "when what worked where"
    • also <ep> apply --history for when you deployed whatever

• is spiritually similar to RoR tho:

  • no docs, messier & more idiosyncratic w rougher edges but more predictible, prunable, composable, & extractable
  • "just a bunch of glue" but less fe/app-level glue, more js-k8s-git-staticanalysis-opencode glue
  • is a POC to be forked, not imported/installed
  • instead of one app-per-repo its one app-per-entrypoint
  • instead of prod|smoke|staging|dev you get unlimited envs just fork an ep
  • conveniences like
    • auto kubectl port-forward for devpc -> k8s(incl minikube) for devserver dbconsole etc
    • sentry-like js exception emails (smtp) & checking w <ep> exceptions (imap)
    • ethereal emails so emails just pop up in new tab when isDevPc

• has grown beyond^ to a "monorepo of apps/infra", represented by entrypoints with actions

  • actions started as k8s apply delete expanded to be like rake tasks <ep> devserver runtests migrate dbbackup etc
  • hit ignition after adding .opencode integration

• has eps for provisioning k8s clusters like Harvester (bare-metal w pxe), Hetzner, DigitalOcean, or Vultr

  • provisioning = external-dns, cert-manager, docker-registry, containerNativePostgres (cnpg), gitssh

• uses js for k8s-resource defs no YAML fts. simple deterministic&idempotent <ep> -> json -> kubectl apply/delete ( no ci/operators/crds yet )

Q: 🤮a js monorepo deploying to k8s? i want my RoR & dokku / handcoded html on github pages!
A: fair enough lol. js is wat (but not as wat as monkey patching or a tangly-ass ball of before_saves) and k8s can seem scary but can actually be simple. it's more generic/self-hostable than vercel/railway/heroku/github (you don't have to pay $ to companies run by people taking selfies w Netanyahu👹). anyways, it's been useful to me & and i'm just sharing, not selling anything other than "🖕 head-in-sand-corpos & mass-murderers"

Q: why k8s over a linux box? A:

• declarative>stateful (json objects>bash commands)
• better primitives IMO (deployment>process, pvc>disk/folder, ingress/external-dns>idk what??)
• node-level fault tolerance like if your mobo/cpu craps out
• you don't need to rewrite your entire infra if you ever wanna scaleup

Q: vibe coded? A:

• hand-coded 2021-2025
  • ~20k loc - eptNextjsApp, eptMjsRunner, eptClusterSync, eptCnPgDb, drawinggame, eptMinecraftSync
  • a few complex apps (todo os them) builtw^ still-deployable-w-peat, eth validator deployers & pt_mv/howimports v0
• hand-prompted 2026+
  • ~50k loc - cli plumbing/DRYing, AST tooling fixes, .opencode, TS types, this gallery, demos & tests
  • os'ing it before ruined w^ :P (jk agents yall were a legit big help)
  • ( started w opus-4.5, now glm & kimi exclusively )

for limiting wasted tokens & blast radius of agent dumbassery:

• agents.md
• séance - agent can chat with a past session to continue its work or debug what went wrong. doubles as a context-saving alternative to compaction
• browser - headless browser (playwright) for screenshots, console errors & network failures, perf traces, heap snapshots & etc
• pt_commit - git commit w file autotracking & per-file locks so concurrent agents know/stop if they step on each other's toes. autosaves opencodeSessionId in commit for seance / opencode -s etc
• pt_mv / pt_rntok / pt_rm - mv/rename/delete w cross-repo ref updates & auto-commit; ocHook blocks raw git rm/mv+sed
• howimports & importers
• wrapped mcp bash to autosummarize(interest-directed) > 600tok & memoize <1hr; interest="raw log"/# bump1 escape hatches
• wc & sc unit responses :)
• how i work with agents

$ ptm <action> [args]
  # movements
  mv         🙏  <from> <to>                     mv/rn & update imports & importers (auto-commits)
  commit     💎  --msg= [--files=...] [--amend]  pt_commit CLI equivalent (for worktree delegation)
  extract    🤲  <exports...> [dest]             extract exports to dest or new file
  rntok      👐  <from> <to>                     rn word codebase-wide (auto-commits)
  subst      🫶  <pattern> <name>                replace pattern, auto-add import if nec

  # info/debug
  resolveimport   <fromFile> <toFile>             compute correct relative import path (avoids depth/extension errors)
  importers     <file> [<importer>] [--epDir]   ls files that directly import tgt
  howimports    <file> [<srcFile|package>] [--epDir]  ls eps that transitively import tgt (or chain from srcFile/pkg)
  lseps         [--epDir=<dir>] [--inclTokens] [--inclNpm]  eps & stats
  bisect        <ep> --good=<sha> [--autorun]   bisect importtree in isolated worktree
  wt            start <name>|--sha=<sha> | done <name> [--discard]  isolated worktree (to dev or checkout SHA)
  check         <files|dirs...>                 check syntax + TS types + boundaries (componentsF can't import serverF etc)
  epsearch      <ep> <pattern> [rg-flags...]    search within ep import tree (uses rg)
  gitlog        <file> [git-log-flags...]       git log limited to file import tree
  ocsearch      <query> [--since=Nd]            search past oc sessions & commits by keyword
  exceptions    [--show=<errHash>] [--test]     exceptions across all eps from IMAP

git clone https://peat.eth.demokluster.com/peat0.git && cd peat0git rev-parse HEAD | head -c 16 # should eq 00074b9842603bcfcorepack enable && corepack pnpm install# then to setup a k8s cluster & deploy gamesapp:mkdir -p data/secrets2echo '{        "CF_API_EMAIL": "your-cf-email@website.com",        "CF_API_KEY": "your-cf-api-key"}' > data/secrets2/external-dns-cf-demokluster.jsoncp ~/Downloads/do2demo-kubeconfig.yaml data/secrets2/do2demo.yaml # get this from digitalocean or your k8s provider# add to data/secrets2 : ipfs-filebase demok_fm_smtp.json demok_fm_imap.json openrouter-gamesdev# prompt opencode w:# "pls setup the cluster then deploy drawinggame.do2demo.yourwebsite.com incl db/prereqs . see your cluster-app-deploy skill. you will need to add a new domain for yourwebsite.com which is part of external-dns-cf-demokluster.json cf account"# (cf is the only external-dns provider rn unfort but that shouldn't be too hard for you to customize)

& non-rigid & consistent & ssot!

first one to fork it to sourceforge wins 5pts :)

# add to your shell rc ( ~/.bashrc or ~/.zshrc etc )export PATH=/path/to/peatSymposium/pt0/path_bin:$PATH # PATH prepend not append to override git to block dumbass agents from reset/stashing'ing or whatever & messing each other up.# also provides user w ptnode, ptm, & clusterClis like do2demo, harv2demo, etcexport DEVPC=1 # enables dev-mode behaviors (ethereal emails, graphql introspection, local disk paths, etc)

Q: ptnode?
A: optional node wrapper to silence hard-to-silence warnings, to impl --saveExample for bashtranscripts for this blog etc. a custom ep for your eps!

Q: do2demo, harv2demo ?
A: optional cluster-specific kubectl alias/wrapper/custom-ep

by pete

• just a lama bean been gardening to fend off specters. "And ye shall be sorrowful, but your sorrow shall be turned into effective devices for computing in any direction." - kingjamesprogramming.tumblr.com / Unsong

with ❤️

• for all the those whose code&art i build with/upon
• & for 🌻

🙏?

• order a bunch of art from one of these artists i love
• &