github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 19:47:47 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2220] Add Healthcheck to Dockerfile #6601

New Issue
Open
opened 2026-04-20 17:12:01 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 17:12:01 -05:00
Owner
Copy Link

Originally created by @momonator25 on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2220

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same feature request.

Description

I found issue #363 from over a year ago marked as "Closed as not planned".
Is there any reason why it should not be implemented?

The corresponding function is already there:

docker exec -it vikunja-app-1 /app/vikunja/vikunja healthcheck returns API server is healthy

I see no downside in having a proper healthcheck in the Dockerfile which is acitve by default.

Which alternatives did you consider using instead?

The already mentioned:

healthcheck:
  test: [ "CMD", "/app/vikunja/vikunja", "healthcheck" ]

should work fine (I use exactly this in my Docker-Compose.yaml)

Originally created by @momonator25 on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2220 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same feature request. ### Description I found [issue #363](https://github.com/go-vikunja/vikunja/issues/363) from over a year ago marked as "Closed as not planned". Is there any reason why it should not be implemented? The corresponding function is already there: `docker exec -it vikunja-app-1 /app/vikunja/vikunja healthcheck` returns `API server is healthy` I see no downside in having a proper healthcheck in the `Dockerfile` which is acitve by default. ### Which alternatives did you consider using instead? The already mentioned: ```yaml healthcheck: test: [ "CMD", "/app/vikunja/vikunja", "healthcheck" ] ``` should work fine (I use exactly this in my `Docker-Compose.yaml`)
GiteaMirror added the area/docker label 2026-04-20 17:12:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/docker
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6601
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?