mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 15:05:49 +03:00
[GH-ISSUE #612] Persist DB using docker hub image #447
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#447
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DierlysCSRodrigues on GitHub (Feb 25, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/612
Hi
First, congratulations for the work!
A question ..
I'm trying to use the docker hub image, to upload the tool in a production environment.
However, as described, this image instantiates a disposable SQLite database.
Is there any way to use this image and persist the DB using postgres or MySQL?
https://hub.docker.com/r/healthchecks/healthchecks
@cuu508 commented on GitHub (Feb 25, 2022):
Yes, you can configure it to use a PostgreSQL or MySQL database using environment variables. See the variables that start with "DB_" here: https://healthchecks.io/docs/self_hosted_configuration/
@P4sca1 commented on GitHub (Mar 3, 2022):
When using MySQL, this will fail, because mysqlclient is missing in
requirements.txt.@DierlysCSRodrigues commented on GitHub (Mar 9, 2022):
Very well observed @P4sca1. I was able to perform the persistence using PostgreSQL. I'll leave the example of my compose:
@cuu508 commented on GitHub (Mar 18, 2022):
I released a new version of Healthchecks (v2.0.1) and published new Docker images. The images now have mysqlclient preinstalled.