Skip to main content
Version: 2.8.1

πŸ–₯️ 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

OptionDescription
--helpDisplay help message
--configPath to configuration file
--systemdSystemd service management
--notifyNotify systemd about readiness
--versionShow 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.

πŸš€ Next Steps​