Where Does Hesk Store Settings and Tickets?
Hesk reads hesk_settings.inc.php for database and folder paths. Tickets live in MySQL; attachments in a writable folder.
Last updated
Hesk centers on hesk_settings.inc.php with MySQL credentials, table prefix, helpdesk URL, and folder names for admin, attachments, and cache. Tickets, staff, and KB articles live in MySQL. Attachments land in a writable attachments/ folder (PHP upload limits apply on top). Cache holds temporary files beside it.
The installer writes the settings file, then must go: delete install/ immediately or it invites database reinitialization over live tickets. Upgrades explicitly exclude the settings file; uploading a fresh copy resets credentials to blanks. Docker images add env-driven DB wiring with attachments and cache volumes; the same file rules apply inside.
Where Hesk stores this, by platform
hesk_settings.inc.php (install root)
DB credentials, URLs, folder names. Installer-written; chmod 666 on need. Exclude from upgrade uploads. Docker takes DB via env with attachments/cache volumes.
Frequently asked questions
how do i back up hesk
Copy hesk_settings.inc.php plus a MySQL dump plus the attachments folder with the app stopped. Tickets reference files by path; one without the others breaks threads or downloads. chmod the settings file 666 and attachments 777 on restore when needed.
should i upload hesk_settings.inc.php on upgrade
Keep it, do not upload it. The file (plus head/header/footer txt) belongs to the running install only; overwriting it on upgrade wipes DB credentials and paths. Exception: renamed admin folders need manual file moves to match.
Notice an outdated path? Let us know.