nextcloud / nextcloud/docker

healthchecks / example

Open
#2,250 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs enhancement examples
Dominant language
Shell
Stars
7.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

Among other things, this may (should) help with some of the timing issues people sometimes report as possible bugs in the Installer.

e.g. (note: do not use this one)

  db: 
    [...]
    healthcheck:
      test: [ "CMD", "healthcheck.sh", "--innodb_initialized" ]
        #start_period: 1m
        #start_interval: 10s
        #interval: 1m
      timeout: 5s
      retries: 6
[...]
  app:
    depends_on:
      db:
        condition: service_healthy
        restart: true
      redis:
        condition: service_started

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue proposes a Docker Compose healthcheck and depends_on example to help investigate Installer timing issues. Start by locating the repository's existing Installer and example configuration entry points; done means the appropriate location and example are established without using the explicitly rejected sample.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.