avi/Orion
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Orion vault — clean initial history

Browse source 
Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on
2026-10-01. Deliberately orphaned: prior history contained a plaintext
password and stays local-only on branch archive/pre-boilerplate-history.
Secrets and live Hermes state are gitignored.
This commit is contained in:
Avi 2026-10-02 08:34:04 -05:00
commit a66996ac10
233 changed files with 103810 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

35
3. Resources/Research/prompts/Prompt Preparing Arch app for Debian.md Normal file
View file

@ -0,0 +1,35 @@
```
I don't know the exact build setup. Inspect the project, tell me what language it is, what dependencies it needs, and write me a Dockerfile that builds a Debian-compatible version and then push to my git
```
That one prompt covers the identification _and_ the Dockerfile in a single step.
---
Docker is only needed on _your_ Arch machine to _build_ the Debian version. Your friends just need the output file.
Think of it like a bakery: you use the oven (Docker) to bake the bread, but your friends just eat the bread.
## What your friends actually need
| You give them | They need to have | They do |
| --------------------------- | ------------------------------------- | -------------------------------------- |
| **`.deb` file** | Nothing extra (it's native to Debian) | `sudo dpkg -i app.deb` or double-click |
| **AppImage** | Nothing extra | `chmod +x app.AppImage` then run it |
| **Static binary** (Go/Rust) | Nothing extra | `chmod +x app` then run it |
None of these require Docker, Node, Python, Go, or any build toolchain on the friend's side. They're just finished, self-contained files.
So the workflow is:
```
Your Arch machine (has Docker)
└── docker build → produces app.deb or AppImage
│
▼
Send the file to friends
│
▼
Friend's Debian machine (no Docker needed)
└── runs the file directly
```