docs(readme): add ZopDay to the deployment options - #2385
muskanbandta23 wants to merge 2 commits into
Conversation
Sorry, something went wrong.
| | Docker Compose | VPS, home servers, and any Docker-capable host | | ||
| | [Railway](https://railway.com/new/template/PwpGcf) | One-click managed hosting | | ||
| | Coolify | Self-hosted PaaS deployments with `docker-compose.coolify.yml` | | ||
| | [ZopDay](https://zop.dev/zopday/app/deploy?image=ghcr.io/capsoftware/cap-web:latest&port=3000) | One-click deploy to ZopCloud or into your own AWS or GCP account | |
There was a problem hiding this comment.
One-click deployment lacks dependencies
The ZopDay link passes only the cap-web image and port. If ZopDay does not provision additional resources, clicking it will deploy without the MySQL database, object storage, and required environment variables that Docker Compose supplies. Cap cannot run as a usable standalone web container. Please link a deployment that includes those dependencies, or explain the setup users must complete.
Prompt To Fix With AIThis is a comment left during a code review.
Path: README.md
Line: 101
Comment:
**One-click deployment lacks dependencies**
The ZopDay link passes only the `cap-web` image and port. If ZopDay does not provision additional resources, clicking it will deploy without the MySQL database, object storage, and required environment variables that Docker Compose supplies. Cap cannot run as a usable standalone web container. Please link a deployment that includes those dependencies, or explain the setup users must complete.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for checking this carefully — I agree with your conclusion. Removing the claim from the PR description addresses the documentation issue, but the README button would still launch only cap-web, without MySQL, object storage, or the media server, so it would not produce a usable Cap instance.
I recommend closing this PR for now rather than merging a misleading deployment option. A future PR with a verified multi-service deployment definition could be useful, provided ZopDay supports the required services, secrets, persistent volumes, and public/internal endpoints; it should be tested end to end before adding the button.
Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.
Sorry, something went wrong.
|
|
||
| [](https://railway.com/new/template/PwpGcf) | ||
|
|
||
| [](https://zop.dev/zopday/app/deploy?image=ghcr.io/capsoftware/cap-web:latest&port=3000) |
There was a problem hiding this comment.
Production URL settings are ignored
The instructions below this direct-image button tell users to set CAP_URL and S3_PUBLIC_URL, but Docker Compose translates those names into the variables the app actually reads: WEB_URL, NEXTAUTH_URL, and S3_PUBLIC_ENDPOINT. If users follow those instructions when deploying the image through ZopDay, the settings will not configure the app, leaving its public URL and storage endpoint unset. Please provide the image-level variable names for this deployment path.
Prompt To Fix With AIThis is a comment left during a code review.
Path: README.md
Line: 105
Comment:
**Production URL settings are ignored**
The instructions below this direct-image button tell users to set `CAP_URL` and `S3_PUBLIC_URL`, but Docker Compose translates those names into the variables the app actually reads: `WEB_URL`, `NEXTAUTH_URL`, and `S3_PUBLIC_ENDPOINT`. If users follow those instructions when deploying the image through ZopDay, the settings will not configure the app, leaving its public URL and storage endpoint unset. Please provide the image-level variable names for this deployment path.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Sorry, something went wrong.
There was a problem hiding this comment.
Also correct, thank you. CAP_URL and S3_PUBLIC_URL are compose-level names that docker-compose.yml maps onto what the image actually reads:
WEB_URL: ${CAP_URL}
NEXTAUTH_URL: ${CAP_URL}
S3_PUBLIC_ENDPOINT: ${S3_PUBLIC_URL}
So the instructions under the table would not apply to a direct-image deploy, exactly as you say. This is part of the same underlying problem as the other comment — a single-image button is the wrong shape for this stack — so rather than patch the variable names I have corrected the body and left the decision with you.
Sorry, something went wrong.
This branch has not been deployed
Reviewers
1 more reviewerAt least 1 approving review is required to merge this pull request.
Summary
Adds one-click deployment with ZopDay to the Deployment Options table, alongside Docker Compose, Railway and Coolify — one table row and one button, matching how the Railway entry is presented.
README.md only, +3/−0.
One-Click Deploy
ZopDay's One-Click Deploy feature lets users quickly deploy an application to ZopCloud or their own cloud via ZopDay, without the usual manual deployment setup.
The feature supports applications from GitHub repositories and Docker images, while Helm Charts can be deployed to the user's own cloud Kubernetes cluster.
Supported deployments
Users can use a shareable deploy link to open an application in ZopDay and deploy it with one click. They can also include preset environment variables, so required configuration fills in automatically when the user opens the deploy link.
Try it out: https://zop.dev/zopday/app/deploy
Overview: https://zop.dev/zopday/oss
What it offers
Click the button and a deploy screen for Cap opens, with ghcr.io/capsoftware/cap-web:latest and port 3000 already set — the same image and port as docker-compose.yml, so it tracks the tag your compose file already uses. Cap also needs MySQL, object storage and the media-server service from docker-compose.yml; the button on its own deploys the web container, so those still have to be provided. Choose ZopCloud to have it run fully managed, or connect your own AWS or GCP account and ZopDay sets it up there instead.
Note that CAP_URL and S3_PUBLIC_URL are compose-level names — the image itself reads WEB_URL, NEXTAUTH_URL and S3_PUBLIC_ENDPOINT, so the instructions under the table do not carry over to a direct-image deploy.
What it adds alongside the existing three
An extra row in the same table rather than a replacement for any of them.
Deploy to ZopDay Button
Notes