global-launcher
Global launcher for Kodachi dashboard binaries with execution folder containment
Version: 9.0.1 | Size: 1.4MB | Author: Warith Al Maawali
License: Proprietary | Website: https://digi77.com
File Information
| Property | Value |
|---|---|
| Binary Name | global-launcher |
| Version | 9.0.1 |
| Build Date | 2025-11-08T18:24:00.610637803Z |
| Rust Version | rustc 1.91.0 (f8297e351 2025-10-28) |
| File Size | 1.4MB |
| JSON Data | View Raw JSON |
SHA256 Checksum
Features
| Feature | Description |
|---|---|
| Feature | Dynamic binary discovery and deployment |
| Feature | Execution folder containment for security |
| Feature | Symlink-based global access |
| Feature | Comprehensive error handling and logging |
| Feature | Support for both Rust and Gambas binaries |
| Feature | Deployment verification and rollback |
| Feature | JSON and text output formats |
| Feature | Zero hardcoded paths - fully dynamic |
Security Features
| Feature | Description |
|---|---|
| Authentication | Integrates with system permissions and user context |
| Encryption | Secure configuration embedded in binary |
| Inputvalidation | All binary names and paths are validated against security rules |
| Ratelimiting | Configurable timeouts prevent resource exhaustion |
System Requirements
| Requirement | Value |
|---|---|
| OS | Linux (Debian-based, specifically Kodachi OS) |
| Privileges | root/sudo for global deployment |
| Dependencies | cli-core library, logs-hook service, symlink support in filesystem |
Global Options
| Flag | Description |
|---|---|
-h, --help |
Print help information |
-v, --version |
Print version information |
-n, --info |
Display detailed information |
-e, --examples |
Show usage examples |
--json |
Output in JSON format |
--json-pretty |
Pretty-print JSON output with indentation |
--verbose |
Enable verbose output |
--quiet |
Suppress non-essential output |
--no-color |
Disable colored output |
--timeout <SECS> |
Set timeout (default: 600) |
--user-override <USERNAME> |
Override target user for deployment |
Commands
Management Commands
deploy
Deploy global symlinks for all dashboard binaries
Usage:
Options:
- --force: Force deployment even if binaries exist
- --no-verify: Skip verification after deployment
- --save-hashes: Save SHA256 hash report to results directory
Examples:
verify
Verify deployed symlinks are working
Usage:
Options:
- --detailed: Show detailed verification info
- --save-hashes: Save SHA256 hash report to results directory
Examples:
cleanup
Remove all deployed symlinks
Usage:
Options:
- --yes: Confirm cleanup without prompting
Examples:
Examples
Deployment Operations
Deploying and managing global binary access
Deploy global access for all dashboard binaries
Expected Output: Creates symlinks in /usr/local/bin for all discovered binariesNote
Requires sudo for writing to /usr/local/bin
Deploy with JSON terminal output
Expected Output: JSON response with deployment results and statistics on terminalDeploy and save SHA256 hash report to results directory
Expected Output: Creates deployment-hashes.json with SHA256 hashes in hooks/results/Note
Includes source binary and launcher hashes for integrity verification
Force deployment, replacing existing symlinks
Expected Output: Overwrites existing symlinks and creates backupsVerification Operations
Verifying deployed symlinks work correctly
Verify all deployed symlinks
Expected Output: Reports on symlink status and any issues foundVerify and save hash report to results directory
Expected Output: Creates verification-hashes.json with SHA256 hashes in hooks/results/Note
Includes source binary hashes and launcher hash for integrity checks
Detailed verification with JSON terminal output
Expected Output: Comprehensive JSON with symlink status and SHA256 hashesNote
Each binary includes source_binary_hash and launcher_hash fields
Hash Integrity Verification
SHA256 hash verification for binary integrity and update detection
Save SHA256 hash report for all deployed binaries
Expected Output: Creates verification-hashes.json in hooks/results/Note
Includes source binary hashes and launcher hash for integrity verification
Deploy binaries and save hash report
Expected Output: Creates deployment-hashes.json in hooks/results/Note
Hash report useful for tracking binary versions and detecting tampering
View saved hash report
Expected Output: JSON report with SHA256 hashes for all binariesNote
Compare hashes between deployments to detect binary changes
Save hash report and extract specific hashes from JSON output
./global-launcher verify --save-hashes --json | jq '.data.verified_symlinks[0] | {name, source_binary_hash, launcher_hash}'
Note
Combine --save-hashes with --json for both file storage and terminal output
Using Global Binaries
Once deployed, binaries work from anywhere
Run health-control from any directory
Expected Output: Executes health-control in hooks directory contextNote
Works from any location after deployment
Run ip-fetch with JSON output globally
Expected Output: IP information in JSON formatList DNS servers from anywhere
Expected Output: DNS server list with current configurationCleanup Operations
Removing global binary access
Remove all deployed symlinks
Expected Output: Removes all symlinks and reports countNote
Requires sudo for removing from /usr/local/bin
Auto-confirm cleanup with JSON terminal output
Expected Output: JSON response with cleanup results on terminalEnvironment Variables
| Variable | Description | Default | Values |
|---|---|---|---|
RUST_LOG |
Set logging level | info | error |
NO_COLOR |
Disable colored output when set | unset | 1 |
KODACHI_BASE_DIR |
Override hooks directory location | auto-detected | /path/to/hooks |
Exit Codes
| Code | Description |
|---|---|
| 0 | Success |
| 1 | General error |
| 10 | Security violation |
| 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 |