Operations

Keep it running.

sudo journalctl -u pepe -f
sudo systemctl restart pepe
pepe status

Back up SQLite on the relay host. Stop the service for a filesystem copy, or use SQLite’s online backup mechanism. Do not copy only the main file while WAL writes are active.

For an update, build the desired current source commit for the server’s platform, then pass that binary explicitly:

pepe upgrade --binary /path/to/new-pepe --check
sudo pepe upgrade --binary /path/to/new-pepe

The installed-service updater backs up state, replaces the executable, restarts the service, and checks health. There is no published release channel. During v0.0, review storage changes before updating; backward compatibility is not promised.

sudo pepe uninstall          # keeps configuration and state
sudo pepe uninstall --purge  # deletes configuration and state

Uninstall leaves Caddy and its route in place. Remove the Pepe proxy route separately when decommissioning the endpoint.

When the string goes quiet

• No certificate: check DNS, inbound ports 80/443, and Caddy logs.
• Unclaimed event: check the exact pepe/… prefix, registered workspace, and same-repository PR origin.
• Repeated delivery: inspect the local receiver’s response. Only a successful 2xx acknowledges it.
• OAuth state mismatch: keep the original application state in the cookie; send only Pepe’s opaque state to Google.

Report a problem in the Pepe source repo ↗