Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nextcloud docker healtheck integration #27

Open
col-panic opened this issue Sep 9, 2024 · 1 comment
Open

Nextcloud docker healtheck integration #27

col-panic opened this issue Sep 9, 2024 · 1 comment

Comments

@col-panic
Copy link
Member

col-panic commented Sep 9, 2024

A docker service should perform some kind of healthcheck on itself and perform a specific action,
like restarting the service or reporting the problem.

Nextcloud in our case is heavily dependent on

  • the database being properly available
  • the S3 storage being correctly reachable and usable

to assert this, we should extend nextcloud.yml or the depending docker image with respective
tests.

A general topic on database healthcheck can be found here docker-library/docs#2391, I could not yet find any information on s3 resp. checks.

As for S3 - we could both solve it for this project, and open up an issue for the general Nextcloud docker image,
as it might be interesting for other users too. https://github.com/nextcloud/server/wiki/How-to-test-S3-primary-storage

@acomdigital
Copy link
Contributor

acomdigital commented Sep 25, 2024

@col-panic Please take a look at the following variant of nextcloud.yml extension.
With some time intervals, the healthcheck.php file checks the availability of DB (by getting dummy data from a current connection) and primary S3 storage (by writing a test file to storage, checking availability, and deleting it).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants