Peppermint

Peppermint is a self-hosted help desk for support teams to track, prioritise, and resolve customer tickets in one central place.

  • Business & Finance
  • Communication
  • Other
Peppermint is a self-hosted help desk for support teams to track, prioritise, and resolve customer tickets in one central place.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

25/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
351 install platform, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM

Based on 3 of 4 factors.

Availability: platform listings confirmed 18 days ago

No GitHub repository data collected yet.

Checked 54 days ago - source: GitHub (BigBearTechWorld/peppermint)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 10 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the database password and secret Before starting Peppermint with Docker (a way to run the app in a container), edit docker-compose.yml and make POSTGRES_PASSWORD and DB_PASSWORD the same strong password: the first is the database password, and the second is the password the app uses to reach that database. Also change SECRET to a long random value, because leaving defaults can let someone access the database or fake logins. source
  • Back up the database folder The example compose file keeps the database (the app's main data store) in a Docker volume named pgdata, which is a saved folder for the database. Keep that volume safe and back it up, because if it goes missing or gets corrupted, Peppermint can lose its records or fail to work properly. source
  • Use a reverse proxy for public access If you plan to access Peppermint by a domain name (like support.example.com), put a reverse proxy (a web server that forwards requests to the app) in front of it and use HTTPS. This keeps people from connecting to the app's direct ports and helps protect logins from eavesdropping. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What database credentials do I need to set when running Peppermint with Docker?

Set POSTGRES_PASSWORD and DB_PASSWORD to the same strong password in docker-compose.yml. POSTGRES_PASSWORD is the database password, while DB_PASSWORD is the password Peppermint uses to reach the database.

Why should I change the SECRET value in the Docker setup?

Change SECRET to a long random value before starting Peppermint. Leaving it at the default can allow someone to access the database or fake logins.

What data should I back up for Peppermint?

Back up the pgdata Docker volume, which the example compose file uses to store the database. If that volume is missing or corrupted, Peppermint can lose its records or fail to work properly.

Should I expose Peppermint directly by a domain name?

If you plan to access Peppermint by a domain name, put a reverse proxy in front of it and use HTTPS. This prevents direct access to the app’s ports and helps protect logins from eavesdropping.

Answers sourced from github.com, github.com

Community

Collected 48 days ago - public community threads