docker compose healthcheck

Open
#346 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no file; start by locating the Docker Compose service and checking the Go application's /health endpoint on port 8080. Compare the proposed command and timing values with the service's behavior, then verify whether the endpoint and healthcheck settings produce the expected container status.

Written by the indexing model from the issue text.

Description

is this the right way to do it?
(It gives me a "healthy" status doing it like this):

healthcheck:
  test: ["CMD-SHELL", "curl -fsS http://localhost:8080/health || exit 1"]
  interval: 60s
  timeout: 5s
  retries: 3
  start_period: 30s

a) right end point?
b) reasonable time settings?

Dominant language
Go
Stars
3.1k
Forks
264
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from rishikanthc/Scriberr

All issues in rishikanthc/Scriberr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.