Global Launcher
🛡️ File Information
| Property | Value |
|---|---|
| Binary Name | global-launcher |
| Version | 9.0.1 |
| File Size | 3.6MB |
| Author | Warith Al Maawali |
| License | Proprietary |
| Category | Infrastructure & Management |
| Description | Global launcher for Kodachi dashboard binaries with execution folder containment |
| JSON Data | View Raw JSON |
SHA256 Checksum
🛡️ Key Features
Service Management
| Feature | Description |
|---|---|
| Deployment Orchestration | Deploys all Kodachi services correctly |
| Execution Containment | Enforces folder-based isolation |
| Version Management | Tracks and updates service versions |
| Process Monitoring | Ensures services are running properly |
Why Global Launcher is Essential
| Benefit | Description |
|---|---|
| Security Isolation | Services cannot write outside their directories |
| Consistent Deployment | All services deployed uniformly |
| Lifecycle Management | Start, stop, restart services systematically |
| Resource Control | Prevents runaway processes and resource leaks |
🛡️ ⚡ TL;DR - Essential Commands
# Deploy global symlinks for all dashboard binaries
sudo ./global-launcher deploy
# Verify deployed symlinks are working
./global-launcher verify
# Remove all deployed symlinks
sudo ./global-launcher cleanup
🛡️ Understanding Service Deployment
Execution Folder Containment
Global Launcher enforces a critical security principle - services can only write to their execution directory:
# Deploy service with containment
sudo ./global-launcher deploy ip-fetch
# Service structure:
# dashboard/hooks/
# ├── ip-fetch/ # Execution directory
# │ ├── ip-fetch # Binary
# │ ├── temp/ # Temporary files
# │ ├── cache/ # Cache data
# │ └── output/ # Results
Security Benefit: Services cannot write to system directories or other service folders.
Deploying Services
# Deploy all dashboard binaries as global symlinks
sudo ./global-launcher deploy
# Deploy with JSON output
sudo ./global-launcher deploy --json
# Force deployment even if binaries exist
sudo ./global-launcher deploy --force
# Deploy without verification
sudo ./global-launcher deploy --no-verify
Service Verification
# Verify all deployed symlinks
./global-launcher verify
# Verify with detailed information
./global-launcher verify --detailed
# Verify with JSON output
./global-launcher verify --json
# What it checks:
# ✓ Symlinks exist and are valid
# ✓ Target binaries are executable
# ✓ Permissions are correct
Cleanup Operations
# Remove all deployed symlinks
sudo ./global-launcher cleanup
# Cleanup without confirmation prompt
sudo ./global-launcher cleanup --yes
# Cleanup with JSON output
sudo ./global-launcher cleanup --json
Deployment Workflow
# Typical deployment workflow
sudo ./global-launcher deploy # Deploy symlinks
./global-launcher verify # Verify deployment
health-control status # Test a deployed binary
# Re-deployment workflow
sudo ./global-launcher cleanup --yes # Remove existing
sudo ./global-launcher deploy --force # Force new deployment
Important Options
# Override target user for deployment
sudo ./global-launcher deploy --user-override kodachi
# Set custom timeout (default: 600 seconds)
./global-launcher verify --timeout 300
# Enable verbose output
./global-launcher verify --verbose
# Disable colored output
NO_COLOR=1 global-launcher verify
Exit Codes
Global Launcher uses specific exit codes for different scenarios:
0 Success
1 General error
2 Invalid arguments
3 Permission denied
4 Binary not found
5 Directory not found
6 Timeout
7 Deployment error
8 Execution error
9 Validation error
10 Security violation
Environment Variables
# Set custom hooks directory
KODACHI_BASE_DIR=/custom/path ./global-launcher verify
# Enable debug logging
RUST_LOG=debug global-launcher deploy
# Disable colored output
NO_COLOR=1 global-launcher verify
JSON Output Examples
# Get deployment status in JSON
sudo ./global-launcher deploy --json
# Pretty-printed JSON output
./global-launcher verify --json-pretty
# Parse JSON with jq
./global-launcher verify --json | jq '.binaries[]'
What Global Launcher Actually Does
Global Launcher creates system-wide symlinks for dashboard binaries:
# After deployment, binaries are available globally:
health-control net-check # Works from anywhere
ip-fetch fetch # No need for full path
dns-switch status # Accessible system-wide
# (Binaries become available in PATH via symlinks created by global-launcher)
# Symlinks are created in system PATH
# Typically /usr/local/bin or similar
🛡️ Automatic Integration with Online-Auth
Global Launcher deployment is automatically handled by the online-auth service during authentication.
How It Works
When you authenticate:
sudo online-auth authenticate
# Global-launcher automatically:
# → Deploys all dashboard binaries
# → Creates system-wide symlinks
# → Verifies deployment success
Manual Deployment Scenarios
| Scenario | Description |
|---|---|
| Troubleshooting | Debugging deployment issues |
| Testing | Running binaries without authentication |
| Recovery | Fixing system problems |
| Customization | Non-standard deployment paths |
Note
For normal usage, authentication handles everything automatically.
🛡️ Advanced Commands
For advanced users who need access to all available commands and options, please refer to the auto-generated command reference which includes:
| Feature | Description |
|---|---|
| Dependency Management | Service dependency management |
| Resource Limits | Resource limit configuration |
| Process Priority | Process priority settings |
| Custom Paths | Custom deployment paths |
| Health Checks | Service health checks |
| JSON Formatting | JSON output formatting |
| CLI Reference | All command-line flags and parameters |
🛡️ Security Notes
Important Security Practices:
| Practice | Description |
|---|---|
| Deployment Verification | Always verify deployments after installation |
| Containment Checks | Regularly check for containment violations |
| Resource Monitoring | Monitor service resource usage |
| Process Cleanup | Clean up orphaned processes regularly |
| Log Review | Review service logs for anomalies |
🛡️ Performance
| Metric | Value |
|---|---|
| Deploy Time | < 2 seconds per service |
| Memory Usage | ~20MB for launcher |
| CPU Usage | < 5% during deployment |
| Verification Speed | < 1 second per service |
| Cleanup Time | 2-5 seconds total |
🛡️ Support
| Resource | Link |
|---|---|
| Website | digi77.com |
| Anonymity Verifier | kodachi.cloud |
| Discord Support | discord.gg/KEFErEx |
| GitHub | github.com/WMAL |