Resource check in install script
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?
Suggest a system status + pre-requisite resource check on Dokploy install script. I wasted a lot of time trying to install Dokploy on a free 1GB Google Cloud e2-micro instance and couldn't figure out what was wrong. There's no error log other than container killed, only repeated unhealthy Dokploy container and CPU stuck at "100%" or "1500%" from I assume NodeJS. It automagic just works on at least a 2GB instance.
Utils like zram + swapfile do not fix the install issue.
Increasing container healthcheck timeout/retries do not fix it.
Coolify's install script just fast-fails/rejects install when resources aren't met like at least 30G space etc. Dokploy should do the same.
Describe the solution you'd like
Bash script should check for min system requirements and fast-fail with reason/min requirements because Dokploy does not install on e2-micro Google Could instance.
Describe alternatives you've considered
None
Additional context
No response
Will you send a PR to implement it?
I suppose I could vibe it. Will I get a % of Dokploy cloud revenue?
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
Start by locating the Bash installation script and reviewing how it reports failed or unhealthy container setup. Define the minimum resource requirements from the installation behavior, then make insufficient systems fail with a clear explanation and verify that supported systems still install successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, docker, node.js
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100