Where Does Peppermint Store Tickets?
Where self hosted Peppermint keeps tickets in database on Linux servers. See the folder table below.
Last updated
Peppermint is ticketing with server storage. The database holds tickets, clients, and replies. Attachments sit beside it in storage.
Same database means same queues. Exact paths vary by Docker installs. Keep backups on schedule. One missing table restores tickets without replies. For moves, stop workers first to avoid split writes during copies. When in doubt, verify paths inside the app before trusting a remembered folder. Screenshots of settings help when support asks for reproduction steps later.
Where Peppermint Tickets stores this, by platform
/var/lib/peppermint (database, paths vary by install)
Tickets live in the server database with reply history. Back up the database stopped. Match releases before restore. Attachments sit beside data.
Frequently asked questions
How do I migrate Peppermint to a new server?
Back up the Peppermint database with services stopped, then install the same release on the new server before restore. Tickets follow the database. Mixed releases can refuse old schemas, so match versions first. Keep API keys separate.
Does Peppermint back up tickets?
Yes, in the server database per ticket with reply history attached. The host holds a working copy plus attachment cache. Views rebuild after restore. Export CSVs from reports for records, since the data directory alone is working state.
Notice an outdated path? Let us know.