This is the wild west. No apologies, just don't set your expectations too high.

Isolated files that can be run directly once they are given execution permissions with chmod +x script_path and are added to the PATH.

#! /usr/bin/env zsh
#! /usr/bin/env -S uv run --script
#! /usr/bin/env python3
#! /usr/bin/env swift

Binary files are compiled for apple silicon from the adjacent script

swift-tool # binary
swift-tool.swift # script

Quick access to overmind-based daemon management for development services.

Location: ~/dev/_daemons/ (manages services via Procfile)

Usage:

dm start -D          # Start all development services in background
dm status            # Check what's running
dm restart anani     # Restart a specific service
dm connect opencode  # View live logs for a service
dm kill              # Stop all services

Services managed:

• opencode (PORT=13370) - Code server
• appligator (PORT=13371) - Full-stack app (FastAPI + Svelte)
• anani (PORT=13372) - SvelteKit app

Tech: Overmind + tmux + Procfile

Docs: See ~/dev/_daemons/README.md for full documentation

Manages system-level services via PM2 (e.g., ttyd).

Location: ~/dev/_daemons/ecosystem.config.js

Usage:

svc start          # Start all services
svc start ttyd     # Start specific service
svc stop ttyd      # Stop service
svc restart ttyd   # Restart service
svc status         # Show status
svc logs ttyd      # Show logs

Tech: PM2 (Node.js process manager)

Use dm (Overmind) for:

• Development services you frequently restart
• Services you need to interact with (live logs, debugging)
• Projects with hot-reload (appligator, anani)
• Services needing colored, real-time output

Use svc (PM2) for:

• System services that should always run
• Services needing log rotation
• Services that should start on boot
• Production-like services (ttyd, reverse proxies)

Both can coexist without conflict - use the right tool for each job.