Where Does Honk Store Data?
Honk keeps a SQLite database with templates beside the binary. Init flow and backup notes.
Last updated
Honk keeps everything next to its binary. The SQLite database sits in the working directory where init ran, commonly a dedicated folder in home or a web root. Templates override from a data/views tree beside it, with docs and manuals alongside.
There is no config file with server settings: init prompts write listen address, server name and credentials straight into the database. That surprises admins hunting for a file to edit. Upgrades mean backing up the database file first, then running the upgrade subcommand in place.
Where Honk stores this, by platform
~/honk/honk.db
Example working dir; yours is wherever init ran. Templates override in data/views beside it. No config file exists: settings live in the DB from init prompts. Back up honk.db stopped, upgrade with ./honk upgrade.
Frequently asked questions
How do I back up a Honk instance?
Copy honk.db from the working directory with the server stopped. That one file holds accounts, posts and settings. Template overrides in data/views travel separately when customized.
Where is the Honk config file?
There is none. Init prompts collect listen address, server name and login into the database directly. Re-run init flows or edit through the admin UI rather than hunting a file.
How do I upgrade Honk safely?
Copy honk.db aside, replace the binary, then run the upgrade subcommand in the working directory. Skipping the backup risks schema migrations with no rollback. Check the docs folder for version notes first.
Notice an outdated path? Let us know.