Deployment Documentation

Follow these instructions to deploy Honeypot Sentry as a persistent, automated background service on Linux environments.

1. Systemd Service Configuration

To ensure the decoy engine and log watcher survive reboots and run reliably, configure them as `systemd` services.

Create the Honeypot Service: `/etc/systemd/system/honeypot.service`

[Unit]
Description=Honeypot Sentry Decoy Engine
After=network.target

[Service]
Type=simple
User=root
WorkingDirectory=/opt/honeypot-sentry
ExecStart=/usr/bin/python3 /opt/honeypot-sentry/honeypot.py
Restart=on-failure

[Install]
WantedBy=multi-user.target
      

Create the Watcher Service: `/etc/systemd/system/sentry-watcher.service`

[Unit]
Description=Honeypot Sentry Log Watcher & Firewall Automator
After=honeypot.service

[Service]
Type=simple
User=root
WorkingDirectory=/opt/honeypot-sentry
ExecStart=/usr/bin/python3 /opt/honeypot-sentry/watcher.py
Restart=on-failure

[Install]
WantedBy=multi-user.target
      

Enable and Start Services:
sudo systemctl daemon-reload
sudo systemctl enable --now honeypot.service sentry-watcher.service

2. OpenClaw Automation Integration

Honeypot Sentry natively hooks into the OpenClaw orchestration pipeline. When a threat threshold is breached, `watcher.py` triggers an event that OpenClaw can intercept.

# Ensure OPENCLAW mapping is enabled in config.ini
[OPENCLAW]
AUTOMATION_ENABLED = True
SYNC_INTERVAL = 60
      

3. Log Management (Logrotate)

To prevent `/var/log/honeypot.log` from consuming disk space, configure logrotate. Create `/etc/logrotate.d/honeypot-sentry`:

/var/log/honeypot.log {
    daily
    rotate 7
    compress
    missingok
    notifempty
    create 0640 root root
}
      