Where Does Isso Store Config and Comments?
Isso reads an INI config (isso.cfg) and stores comments in SQLite. Docker splits them across /config and /db mounts.
Last updated
Isso configures through an INI file (isso.cfg/isso.conf): database path, site hosts for CORS, listen address, SMTP, moderation. Comments live in SQLite at dbpath, defaulting to /tmp (production guides insist on /var/lib/isso/comments.db or /db/comments.db in Docker). Docker images commonly split /config and /db into separate mounts.
The host list deserves attention: only listed domains may embed comments, with no wildcard, so migrations need the new domain added before DNS flips. Moderation queues, hashes, and karma persist in SQLite; the INI holds no comment data at all. Pass the file with -c or ISSO_SETTINGS env, and keep both halves versioned together.
Where Isso stores this, by platform
isso.cfg (config mount)
Hosts, listen, SMTP, moderation, dbpath pointer. Pass via -c flag or ISSO_SETTINGS. Docker mounts at /config. Hosts have no wildcard, so add new domains before cutover.
/db/comments.db (SQLite)
Comments, moderation, hashes in SQLite. Defaults to /tmp; set a persistent dbpath always. Auto-creates on start. Back with the config as one unit.
Frequently asked questions
how do i back up isso comments
Copy isso.cfg (or .conf) plus the SQLite file from dbpath with the app stopped. Comments, moderation state, and hashes travel in the db; hosts and SMTP in the config. Restore both to matching paths.
why did all my isso comments vanish after reboot
Set dbpath to a persistent path (e.g. /db/comments.db in Docker, /var/lib/isso elsewhere). Defaults point at /tmp, which evaporates on reboot. The file auto-creates, so a missing db usually means a wrong path, not corruption.
Notice an outdated path? Let us know.