44
55- ` ./install.sh ` - Initialize workstation with development tools (bootstrap)
66- ` ./install.sh --install-path /custom/path ` - Install to custom directory
7- - ` ./revenue init ` - Initialize workstation (alternative method )
7+ - ` ./revenue init ` - Initialize workstation (delegates to install.sh )
88- ` ./revenue init --install-path /custom/path ` - Initialize with custom installation path
99- ` ./revenue update ` - Update existing tools and packages
1010- ` ./revenue help ` - Show usage help
11- - ` revenue init|update|demo ` - Global command after setup
11+ - ` revenue init|update|demo|help ` - Available global commands after setup
1212
1313## Demo Management Commands
1414
1515- ` revenue demo start <language> <framework> ` - Start a demo application
1616- ` revenue demo start all ` - Start all demo applications
1717- ` revenue demo stop <language> <framework> ` - Stop a specific demo
1818- ` revenue demo stop all ` - Stop all running demos
19+ - ` revenue demo restart <language> <framework> ` - Restart a demo application
20+ - ` revenue demo restart all ` - Restart all running demo applications
1921- ` revenue demo logs <language> <framework> ` - View logs from a running demo
2022- ` revenue demo connect <language> <framework> ` - Connect to a running demo session
21- - ` revenue demo list ` - List all available demos
23+ - ` revenue demo list ` - List all available demos and their status
2224- ` revenue demo running ` - List currently running demos
23- - ` revenue demo clean --confirm ` - Reset demo directory
25+ - ` revenue demo clean --confirm ` - Force cleanup all processes and sockets
26+ - ` revenue demo reset --confirm ` - Reset to clean git state
27+ - ` revenue demo help ` - Show demo usage help
2428- Direct usage: ` cd amp_demos && ./demo <command> `
2529
2630## Architecture
@@ -39,30 +43,40 @@ The demo system manages multiple language/framework combinations using an Overmi
3943
4044- ** Discovery** : Scans ` amp_demos/ ` for directories containing ` Procfile ` configuration files
4145- ** Process Management** : Uses Overmind with tmux sessions to manage demo processes
42- - ** Tool Management** : Integrates with ` mise ` for per-demo tool installation
46+ - ** Tool Management** : Integrates with ` mise ` for per-demo tool installation and automatic trusting
4347- ** Directory Structure** : ` amp_demos/<language>/<framework>/Procfile `
4448
4549Each demo application must have:
50+
4651- ` Procfile ` - Standard Heroku-style process definition file
4752- ` .env ` - Environment variables (PORT, LANGUAGE, FRAMEWORK)
4853- Optional: ` .mise.toml ` or ` .tool-versions ` for tool requirements
4954
55+ The system automatically:
56+
57+ - Trusts mise configurations silently
58+ - Installs tools and dependencies before starting demos
59+ - Cleans up socket files when starting/stopping
60+ - Provides URL information based on PORT from .env file
61+
5062#### Demo Configuration Format
5163
5264##### Procfile (standard Procfile format)
65+
5366``` Procfile
5467setup: pnpm install --silent # Optional: dependency installation command
5568web: pnpm start # Required: command to start the web process
5669```
5770
5871##### .env (environment variables)
72+
5973``` env
6074PORT=3000
6175LANGUAGE=javascript
6276FRAMEWORK=react
6377```
6478
65- Demo sessions are named as ` <language>-<framework> ` and managed by Overmind using tmux for process isolation .
79+ Demo processes are managed individually (not as named sessions) with Overmind handling the tmux session management automatically .
6680
6781## Code Style
6882
0 commit comments