Healthcheck setup is confusing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Spent hours and hours trying to figure out why my healthchecks arent working at all. It started in the docs, where I was told to past the whole json object, but thats not possible with the current ui on dokploy.
No see the example given in the ui, I thought okay then Ill just copy the whole thing and it should work like the example like this:
And thats where I had to spend hours to figure out why its not working, with help of AI ofcourse. Turns out I have to add commands in the ui and type every command with no quotes or anything like shown by the placeholders:
Describe the solution you'd like
I immedietly knew how to fix this once I clicked on the add command just out of curiosity and saw the second placeholder. So a simple fix is to just show both fields by default so its not ambiguous how the commands should be typed, in one line, with quotes or without, with brackets or without..etc.
The docs have to also be updated to match Dokploy's ui.
Describe alternatives you've considered
The solutions above are straightforward.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the healthcheck setup UI and its documentation, then compare the command-field placeholders and current instructions. Done means the UI clearly exposes both command fields by default and the docs describe the same input format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100