[GH-ISSUE #526] Question: Running in production with sqlite #382

New issue

Closed

opened 2026-02-25 23:42:15 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 23:42:15 +03:00

Owner

Originally created by @jmichalek132 on GitHub (Jun 15, 2021).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/526

Hi, I wanted to ask if it's okay / safe to run in production with sqlite instead of postgres or mysql for simplicity. We would be okay in this case to run it in single replica.

Originally created by @jmichalek132 on GitHub (Jun 15, 2021). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/526 Hi, I wanted to ask if it's okay / safe to run in production with sqlite instead of postgres or mysql for simplicity. We would be okay in this case to run it in single replica.

kerem closed this issue

2026-02-25 23:42:15 +03:00

kerem commented

2026-02-25 23:42:16 +03:00

Author

Owner

@cuu508 commented on GitHub (Jun 15, 2021):

SQLite is one of the database backends that Django officially supports. Healthchecks test suite passes with SQLite. So it "nominally works". I have not used Healthchecks with SQLite in production, and don't know if there would be any issues.

@cuu508 commented on GitHub (Jun 15, 2021): SQLite is one of the database backends that Django [officially supports](https://docs.djangoproject.com/en/3.2/ref/databases/). Healthchecks test suite [passes with SQLite](https://github.com/healthchecks/healthchecks/runs/2734011855). So it "nominally works". I have not used Healthchecks with SQLite in production, and don't know if there would be any issues.

kerem referenced this issue

2026-02-25 23:43:29 +03:00

[GH-ISSUE #1091] Consider allowing SITE_ROOT to be used to configure "base path" as well #758