Where Does Cypht Store Settings and Data?
Where Cypht keeps user settings, attachments, and config on a self-hosted server, plus backup notes.
Last updated
Cypht splits server state three ways: user settings in files or database tables, attachments in their own folder, and app data with module configs. Defaults point under /var/lib/hm3 outside the document root. A .env file drives the whole layout.
User setting files encrypt with login passwords, so backups need passwords alongside files. Docker and source installs share the same directory logic with different prefixes. Keep data outside served paths; the webserver writes there constantly. Audit permissions after every deploy.
Where Cypht stores this, by platform
/var/lib/hm3/users
Default home for users settings, attachments, and app_data outside the document root. File mode encrypts per-user files with login passwords. Database mode swaps files for tables. Back up .env plus data with services stopped.
Frequently asked questions
how do I back up Cypht
Copy the .env file plus the users, attachments, and app_data folders with services stopped. User files encrypt with login passwords, so keep those too. Database-backed setups dump the settings tables instead of files.
file or database for user settings
Set user_config_type to file with a writable users directory outside the document root. Database mode stores the same in hm_user_settings tables. File mode migrates by copying folders; database mode dumps tables.
can Cypht live in the document root
No. Source lives outside the document root with only the generated site linked in. Settings, attachments, and app data must all sit outside served paths. The webserver needs write on data dirs and read on source.
Notice an outdated path? Let us know.