feat: implement overmind-based demo manager

- Convert all demo.yaml configs to Procfile + .env format
- Maintain all existing functionality while leveraging overmind features

The new system provides:
- Better process management with overmind
- Uses the standard Procfile format
- Simplified maintenance and debugging
- Color-coded logs and improved UX
- Easiliy add DB functionality to individual apps

Amp-Thread-ID: https://ampcode.com/threads/T-e1bc82e9-1bdd-44ec-94cb-6e5d264984f6
Co-authored-by: Amp <amp@ampcode.com>

Author: trly

AGENTS.md

@@ -3,16 +3,21 @@
 ## Build/Test Commands
 
 - `./install.sh` - Initialize workstation with development tools (bootstrap)
+- `./install.sh --install-path /custom/path` - Install to custom directory
 - `./revenue init` - Initialize workstation (alternative method)
+- `./revenue init --install-path /custom/path` - Initialize with custom installation path
 - `./revenue update` - Update existing tools and packages  
 - `./revenue help` - Show usage help
 - `revenue init|update|demo` - Global command after setup
 
 ## Demo Management Commands
 
 - `revenue demo start <language> <framework>` - Start a demo application
+- `revenue demo start all` - Start all demo applications
 - `revenue demo stop <language> <framework>` - Stop a specific demo
 - `revenue demo stop all` - Stop all running demos
+- `revenue demo logs <language> <framework>` - View logs from a running demo
+- `revenue demo connect <language> <framework>` - Connect to a running demo session
 - `revenue demo list` - List all available demos
 - `revenue demo running` - List currently running demos
 - `revenue demo clean --confirm` - Reset demo directory
@@ -26,32 +31,38 @@ Key components:
 
 - `revenue` - Single, self-contained setup script with all logic integrated
 - `Brewfile` - Homebrew dependency management (formulae, casks, VS Code extensions)
-- `amp_demos/demo` - Demo application manager using tmux sessions
+- `amp_demos/demo` - Demo application manager using Overmind process manager
 
 ### Demo System Architecture
 
-The demo system manages multiple language/framework combinations using a config-based approach:
+The demo system manages multiple language/framework combinations using an Overmind-based approach:
 
-- **Discovery**: Scans `amp_demos/` for directories containing `demo.yaml` configuration files
-- **Session Management**: Uses tmux with server name "revenue-demo" to isolate sessions
-- **Tool Management**: Integrates with `mise` for per-demo tool installation and YAML parsing
-- **Directory Structure**: `amp_demos/<language>/<framework>/demo.yaml`
+- **Discovery**: Scans `amp_demos/` for directories containing `Procfile` configuration files
+- **Process Management**: Uses Overmind with tmux sessions to manage demo processes
+- **Tool Management**: Integrates with `mise` for per-demo tool installation
+- **Directory Structure**: `amp_demos/<language>/<framework>/Procfile`
 
 Each demo application must have:
-- `demo.yaml` - Configuration file specifying how to start the application
+- `Procfile` - Standard Heroku-style process definition file
+- `.env` - Environment variables (PORT, LANGUAGE, FRAMEWORK)
 - Optional: `.mise.toml` or `.tool-versions` for tool requirements
 
 #### Demo Configuration Format
 
-```yaml
-language: javascript    # Language identifier
-framework: react       # Framework identifier  
-port: 3000            # Application port (for URL display)
-install: pnpm install --silent  # Optional: dependency installation command
-start: pnpm start     # Required: command to start the application
+##### Procfile (standard Procfile format)
+```Procfile
+setup: pnpm install --silent  # Optional: dependency installation command
+web: pnpm start               # Required: command to start the web process
 ```
 
-Demo sessions are named as `<language>-<framework>` and run in tmux for easy management.
+##### .env (environment variables)
+```env
+PORT=3000
+LANGUAGE=javascript
+FRAMEWORK=react
+```
+
+Demo sessions are named as `<language>-<framework>` and managed by Overmind using tmux for process isolation.
 
 ## Code Style
 

Brewfile

@@ -8,6 +8,7 @@ brew "jq"
 brew "mise"
 brew "python"
 brew "tmux"
+brew "overmind"
 brew "tree" 
 brew "yq"
 

DETAILS.md

@@ -3,6 +3,15 @@
 This list is everything that will be installed on your workstation when running
 the installer. All dependencies are managed via [Brewfile](/Brewfile).
 
+By default, the repository is installed to `~/revenue`, but you can customize this 
+with the `--install-path` flag:
+
+```bash
+./install.sh --install-path /custom/path
+# or
+revenue init --install-path /custom/path
+```
+
 To update existing installed tools, run `revenue update`
 
 ## Editors and IDEs
@@ -61,6 +70,12 @@ Command-line interface for Amp AI coding assistant
 mise allows you to easily install additional developer tools as well a manage
 multiple versions of tools globally or,specific to individual projects.
 
+### overmind
+
+overmind is a process manager for Procfile-based applications and tmux sessions. It provides a simple way to manage multiple processes during development with features like process restart, log aggregation, and easy process interaction.
+
+[Learn more](https://github.com/DarthSim/overmind)
+
 ```bash
 revenue on  main [!?] took 12s
 ❯ mise list

README.md

@@ -1,6 +1,7 @@
 # Sourcegraph Revenue Team Workstation Setup
 
-Complete macOS workstation setup for Revenue team members. Installs all tools needed for demos and development.
+Complete macOS workstation setup for Revenue team members. Installs all tools
+needed for demos and development.
 
 ## Quick Start
 
@@ -12,7 +13,7 @@ Complete macOS workstation setup for Revenue team members. Installs all tools ne
 
 **That's it!** The installer will:
 
-- Download this repository to `~/revenue`
+- Download this repository to `~/revenue` (customizable with `--install-path`)
 - Install all necessary tools (VS Code, Python, Java, etc.)
 - Set up demo applications
 - Take about 15-30 minutes
@@ -25,29 +26,7 @@ Once setup is complete, you can use the `revenue` command:
 revenue demo list        # See available demo apps
 revenue demo start python flask  # Start a specific demo
 revenue update          # Update tools to latest versions
-```
-
-## Demo Applications
-
-Quick commands for managing demo applications:
-
-```bash
-# Start any demo
-revenue demo start <language> <framework>
-revenue demo start python flask
-revenue demo start javascript react
-
-# Stop demos
-revenue demo stop python flask
-revenue demo stop all
-
-# View available demos
-revenue demo list
-revenue demo running
-
-# View logs and attach to sessions
-revenue demo logs python flask
-revenue demo attach python flask
+revenue init --install-path /custom/path  # Reinstall to custom location
 ```
 
 See [amp_demos/README.md](amp_demos/README.md) for complete demo documentation.
@@ -56,21 +35,21 @@ See [amp_demos/README.md](amp_demos/README.md) for complete demo documentation.
 
 ### Common Issues
 
-**"Command not found: revenue"**
+#### "Command not found: revenue"
 
 - Close and reopen Terminal, or run: `source ~/.zshrc`
 
-**"Cannot clone repository"**
+#### "Cannot clone repository"
 
 - Ensure you have access to GitHub and the Sourcegraph organization
-- Ask in [#ask-tech-ops](https://sourcegraph.slack.com/archives/C01CSS3TC75) for repository access
+- Ask in [#ask-tech-ops](https://sourcegraph.slack.com/archives/C01CSS3TC75)
 
-**Installation fails with network errors**
+#### Installation fails with network errors
 
 - Check VPN/proxy settings
 - Rerun the installer - it's safe to run multiple times
 
-**"Xcode Command Line Tools required"**
+#### "Xcode Command Line Tools required"
 
 - Run: `xcode-select --install`
 - Wait for installation to complete, then rerun the installer
@@ -81,7 +60,8 @@ If you're stuck:
 
 1. Check the error message for specific guidance
 2. Try running the installer again (it's safe to repeat)
-3. Ask in [#ask-tech-ops](https://sourcegraph.slack.com/archives/C01CSS3TC75) with the error details
+3. Ask in [#discuss-field-engineering](https://sourcegraph.slack.com/archives/C095PTMTS31)
+with the error details
 
 ## Manual Setup (Alternative)
 
@@ -95,7 +75,24 @@ xcode-select --install
 git clone https://github.com/sourcegraph/revenue.git ~/revenue
 cd ~/revenue
 
-# 3. Run setup
+# 3. Run setup (default location)
+./install.sh
+
+# OR: Custom installation path
+./install.sh --install-path /custom/path
+```
+
+### Custom Installation Path
+
+To install the repository to a different location:
+
+```bash
+# Download installer directly
+curl -fsSL https://raw.githubusercontent.com/sourcegraph/revenue/main/install.sh | bash -s -- --install-path /custom/path
+
+# Or clone first and run locally (recommended for custom paths)
+git clone https://github.com/sourcegraph/revenue.git /custom/path
+cd /custom/path
 ./install.sh
 ```
 

amp_demos/README.md

@@ -1,37 +1,46 @@
 # Demo Application Manager
 
-The demo application manager allows running multiple language/framework demos in
-isolated tmux sessions using configuration files.
+The demo application manager allows running multiple language/framework demos
+using [Overmind](https://github.com/DarthSim/overmind)
 
 ## Directory Structure
 
 The script expects demo applications to be organized as:
 
-```
+```text
 amp_demos/
-├── demo
+├── demo                 # Overmind-based demo manager
 ├── <language>/
 │   └── <framework>/
-│       ├── demo.yaml        # Required configuration file
-│       ├── .mise.toml       # Optional: tool requirements
-│       └── ...              # Your demo files
+│       ├── Procfile     # Required: Overmind process definition
+│       ├── .env         # Required: Environment variables (PORT, etc.)
+│       ├── .mise.toml   # Optional: tool requirements
+│       └── ...          # Your demo files
 ```
 
-Only directories containing `demo.yaml` are recognized as valid demos.
+Only directories containing `Procfile` are recognized as valid demos.
 
 ## Configuration Format
 
-Each demo requires a `demo.yaml` configuration file:
+Each demo requires a `Procfile` and `.env` file:
+
+### [Procfile](https://devcenter.heroku.com/articles/procfile) (standard Procfile format)
+
+```Procfile
+setup: pnpm install --silent
+web: pnpm start
+```
+
+#### .env (environment variables)
 
-```yaml
-language: javascript    # Language identifier
-framework: react       # Framework identifier  
-port: 3000            # Application port (for URL display)
-install: pnpm install --silent  # Optional: dependency installation command
-start: pnpm start     # Required: command to start the application
+```env
+PORT=3000
+LANGUAGE=javascript
+FRAMEWORK=react
 ```
 
-The `install` field is optional and runs before the `start` command. The `port` field is used to display the application URL.
+The `setup` process is optional and runs before starting the `web` process. The
+`PORT` variable is used to display the application URL.
 
 ## Usage
 
@@ -80,8 +89,8 @@ cd amp_demos
 ### View and Interact with Demos
 
 ```bash
-./demo logs <language> <framework>    # View current logs from a running demo
-./demo attach <language> <framework>  # Attach to a running demo session
+./demo logs <language> <framework>    # View logs from a running demo
+./demo connect <language> <framework> # Connect to a running demo session
 ```
 
 ### List Demos
@@ -99,11 +108,12 @@ cd amp_demos
 
 ## How It Works
 
-1. **Discovery**: Scans subdirectories for `demo.yaml` configuration files
+1. **Discovery**: Scans subdirectories for `Procfile` configuration files
 2. **Environment**: Runs `mise install` in each demo directory (if available)
-3. **Config Parsing**: Reads the demo configuration using `yq`
-4. **Session Management**: Creates isolated tmux sessions named `<language>-<framework>`
-5. **Execution**: Runs install and start commands within the mise environment
+3. **Config Parsing**: Uses standard Procfile format and `.env` files
+4. **Process Management**: Uses Overmind to manage processes with tmux sessions
+named `<language>-<framework>`
+5. **Execution**: Runs setup and web processes as defined in Procfile
 
 ## Examples
 
@@ -117,8 +127,8 @@ cd amp_demos
 # View logs from a running demo
 ./demo logs python flask
 
-# Attach to running demo
-./demo attach python flask
+# Connect to running demo
+./demo connect python flask
 
 # Stop all demos
 ./demo stop all
@@ -127,12 +137,17 @@ cd amp_demos
 ./demo list
 ```
 
-## Tmux Session Management
+## Process Management
 
-All demos run in a shared tmux server named `revenue-demo`. Sessions are automatically named using the pattern `<language>-<framework>`.
+Overmind manages all demos using tmux sessions named using the pattern
+`<language>-<framework>`. Each demo runs its processes as defined in the Procfile.
 
-To manually attach to a running demo:
+To manually connect to a running demo process:
 
 ```bash
-tmux -L revenue-demo attach -t <session-name>
-```
+cd <language>/<framework>
+overmind connect web -s <language>-<framework>
+
+# Or using tmux directly
+tmux attach -t <language>-<framework>
+