π₯οΈ Command Line
Running Jibril from the command line is the simplest way to get started. Perfect for quick testing, development, and single-server deployments. This method is ideal when you need fine-grained control and want to customize Jibril's behavior to your specific requirements.
π Quick Startβ
1οΈβ£ Download Jibrilβ
Download Jibril:
sudo curl -L -o /usr/bin/jibril https://github.com/garnet-org/jibril-releases/releases/download/v2.8/loader
Make executable:
sudo chmod +x /usr/bin/jibril
Check version:
jibril --version
2οΈβ£ Run Jibrilβ
β‘ Default Configurationβ
Run with built-in defaults:
sudo jibril
- Uses default detection rules
- Outputs to stdout
- No configuration file needed
βοΈ Custom Configurationβ
Run with your own config:
sudo jibril --config /path/to/config.yaml
- Custom detection rules
- Flexible output options
- Fine-tuned performance
π Configuration Fileβ
Create a custom configuration file to tailor Jibril's behavior:
# Create config directory
sudo mkdir -p /etc/jibril
# Create configuration file
sudo vi /etc/jibril/config.yaml
π See Configuration Guide for detailed configuration options.
π Stopping Jibrilβ
When running in the foreground:
# Press Ctrl+C to stop gracefully
When running in the background:
# Find process ID
ps aux | grep jibril
# Stop process
sudo kill <PID>
βοΈ Command-Line Optionsβ
Available Options
| Option | Description |
|---|---|
--help | Display help message |
--config | Path to configuration file |
--systemd | Systemd service management |
--notify | Notify systemd about readiness |
--version | Show version information |
π Tips & Best Practicesβ
β Best Practicesβ
- π Start with default config, customize gradually
- π§ͺ Test new configs before production
- π Monitor resource usage during testing
- π Use version control for config files
β οΈ Common Pitfallsβ
- β Don't run without root/capabilities
- β Don't modify config while running
- β Don't ignore resource warnings
- β Don't use debug mode in production
π Upgradingβ
To upgrade to a newer version:
# Stop current instance (if running)
sudo killall jibril
# Download new version
sudo curl -L -o /usr/bin/jibril https://github.com/garnet-org/jibril-releases/releases/download/v2.8/loader
# Make executable
sudo chmod +x /usr/bin/jibril
# Verify new version
jibril --version
# Restart with your config
sudo jibril --config /etc/jibril/config.yaml
Systemd installation creates files under
/etc/jibril/directory. Newer versions might need to update those files. Make sure to backup the files before updating.