Dokploy - #7893
Conversation
… dispose The ChildProcess setInterval (every 5s) for parent PID health checks was never cleared, causing 'parent process X died' to print indefinitely after the parent died. The repeated _onDispose emission also prevented clean shutdown. - Store interval reference and clear it immediately when parent is detected dead - Also clear on dispose from any source (SIGINT, SIGTERM) - Add fake timer cleanup to test to avoid open handle
- Replace 6 individual subdirectory mounts with single code-server-data volume - Remove user: root (let container run as coder user by default) - Remove duplicate env vars (DISABLE_UPDATE_POPUP, DISABLE_DASHBOARD, DISABLE_STARTUP_PAGE) - Update README with single-volume explanation and migration guide - Update fix-permissions.sh for new single-volume layout
… startup-page - DISABLE_EXTENSIONS default changed from true to false (was blocking all extensions including opencode) - Add DISABLE_STARTUP_PAGE back as configurable env var (was lost during cleanup) - Add DISABLE_EXTENSIONS and DISABLE_STARTUP_PAGE to .env - Update README feature flags and backup instructions
- Fork opencode from anomalyco/opencode to kt-production-repo/opencode - Create dokploy/Dockerfile that extends codercom/code-server:latest and pre-installs opencode CLI - Update docker-compose.yml to build from the new Dockerfile - Update README with opencode usage instructions
Dokploy's build context resolves to the repo root, not the compose file directory. Moved Dockerfile to repo root so the build can find it.
The opencode install script (curl | sh) does not support linux/aarch64. Switched to npm install -g opencode-ai@latest which is cross-platform. Removed old dokploy/Dockerfile (moved to repo root).
The codercom/code-server image bundles its own Node.js internally and does not expose npm globally. Added apt-get install npm before the opencode npm install.
…d user data; improve Dockerfile comment; update docs
|
Was this meant to be pushed elsewhere? Not sure what this Dokploy stuff is. It does look like the PR contains some fixes though, so if you want to open PRs for just those with descriptions I would be happy to review those. |
Hi Asher,Thank you for your response and for offering to review the fixes.To clarify, I am not a developer or programmer by profession. I simply enjoy experimenting with new tech experiences, which is why my repository setup might not look standard.Dokploy is a tool designed to simplify application and database deployments. Since the original repository did not include a YAML file for this type of deployment, I was trying to make it work by adding it as an additional folder. |
2 participants
Fixes #