systemd --user. As on Windows, the bot must run as the user who owns the
sbx daemon and its credentials.
1. Host bootstrap
- Install
sbx(Docker Sandboxes), then log in and initialize the network policy:Celly targetssbx>= 0.45.0. - Install Node 24 with
fnm(ornvm): - Register provider credentials used by the sandboxed agent (see
Providers):
2. Install and configure
~/.bot-celly/.env. The required values are documented in
Configuration.
3. systemd user service
Install globally first withnpm install -g bot-celly. Create
~/.config/systemd/user/celly.service:
bash -lc loads your shell profile so fnm/nvm and sbx are on PATH;
exec keeps the CLI as the main process so SIGTERM reaches Celly’s shutdown
handler. Enable it and keep it running after logout:
4. Verifying a deployment
sbx diagnosereports a healthy daemon and authentication.systemctl --user status cellyisactive (running).curl -s http://127.0.0.1:4560/api/healthreturns{"ok":true,...}.~/.bot-celly/data/bot.logshows the preflight passing and the Discord client logging in.
5. Troubleshooting
6. Admin, backups, and paths
- The loopback admin page, log rotation, SQLite backups, and restore are covered in Operations.
- The sensitive-path denylist and
PROJECTS_ROOTcontainment are covered in Configuration. - Known limitations are listed in Limitations.