orphelix start
Start Orphelix Kubernetes Dashboard in background mode using pm2.Usage
Options
| Option | Alias | Description | Default |
|---|---|---|---|
--port | -p | Port number | 3000 or $ORPHELIX_PORT |
--name | -n | Instance name | orphelix |
Examples
Basic Start
Custom Port
http://orphelix.local:8080
Named Instance
First Run Behavior
On first run,orphelix start automatically:
- Checks dependencies - Verifies Node.js version and kubectl
- Installs packages - Runs
npm installifnode_modulesmissing - Builds application - Runs
npm run build:standaloneif build missing - Initializes database - Creates
orphelix.dbSQLite database - Configures hostname - Prompts to set up
orphelix.local(requires sudo) - Starts pm2 process - Runs main app + notification worker
What Gets Started
The start command launches two pm2 processes:1. Main Application
- Name:
orphelix(or custom name) - Process: Next.js standalone server
- Port: 3000 (or custom)
- Purpose: Web UI and API
2. Notification Worker
- Name:
orphelix-notifications(or{name}-notifications) - Process: Background worker
- Purpose: Desktop notifications for critical issues
Output
Successful start shows:Environment Variables
ORPHELIX_PORT
Set default port via environment variable:--port overrides environment variable:
Hostname Configuration
On first run, you’ll be prompted:- Yes (Y): Adds entry to
/etc/hosts, enableshttp://orphelix.local:3000 - No (n): Skip configuration, use
http://localhost:3000only
/etc/hosts:
Database Initialization
Creates SQLite database at./orphelix.db with:
- User settings (theme, mode, preferences)
- GitHub integration settings
- Cluster aliases
- Critical issues monitoring config
- Sidebar pins
- Notification preferences
Process Management
After starting, the application runs as a daemon via pm2:- ✅ Runs in background (no need to keep terminal open)
- ✅ Auto-restart on crash
- ✅ Logs managed by pm2
- ✅ Survives terminal close
Error Handling
Port Already in Use
kubectl Not Found
Node Version Too Old
Already Running
Post-Start Actions
After starting successfully:1. Open in Browser
2. View Logs
3. Check Status
4. Enable Auto-Startup (Optional)
To start automatically on system boot:Related Commands
- stop - Stop the application
- restart - Restart the application
- status - Check if running
- logs - View logs
- list - List all instances
- startup - Enable auto-startup