Where Does Flood Store Config and Data?
Flood reads config.js (copied from template) with users and history in /data. rTorrent connects over SCGI beside it.
Last updated
Flood centers on config.js (copied from config.template.js, mandatory): rTorrent SCGI host/port or socket, JWT secret, port, baseURI for subpath proxying. User accounts and download history live in the /data volume database. SSL key/cert optionally sit in /data too. rTorrent itself stays a separate daemon Flood talks to, never inside.
Version lineage matters: classic Flood-UI builds need the file; the jesec v4 rewrite configures via CLI and web UI instead. Torrents must be visible at identical paths to client and Flood or file operations silently target wrong files. Rebuild static assets after baseURI changes; the value bakes into served files.
Where Flood stores this, by platform
config.js (install root)
SCGI connection, JWT secret, port, baseURI. Copy from template; required file on classic builds. v4 uses CLI/web instead. Rebuild assets after baseURI edits.
Frequently asked questions
how do i back up flood
Copy config.js plus the /data volume (user db, history, SSL files) with the app stopped. Torrent content stays in rTorrent; Flood holds accounts and history only. Restore both to matching paths.
how do i create the flood config file
Copy config.template.js to config.js and set the SCGI host/port plus a long JWT secret. v4 (jesec) moved to CLI args and web setup; classic Flood-UI builds still require the file. Check the template on updates; new keys arrive regularly.
Notice an outdated path? Let us know.