docs(readme): add ZopDay to the One-Click Deploy options

[muskanbandta23]

Description

Adds one-click deployment with ZopDay to the One-Click Deploy section, alongside Koyeb, Render, Railway, Sealos, DigitalOcean, CapRover, Fly.io and Dokploy.

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

• GitHub Repositories → ZopCloud / Own Cloud via ZopDay
• Docker Images → ZopCloud / Own Cloud via ZopDay
• Helm Charts → Own Cloud Kubernetes clusters only

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

Type of Change

• Documentation update

Related Issue

N/A

What changed

Added a ninth entry to the existing One-Click Deploy section, matching the style of the other providers (Koyeb/Render/Railway/Sealos/DigitalOcean/CapRover/Fly.io/Dokploy): the intro sentence now names ZopDay, the badge joins the list with the same two-space line break as its neighbours, and a > **ZopDay:** note sits with the existing provider notes.

README.md only, +4/−1. Same shape as the Sealos addition in #296 and the DigitalOcean button in #230.

What it offers

Click the button and a deploy screen for LibreDB Studio opens, with ghcr.io/libredb/libredb-studio:latest and port 3000 already set. Choose ZopCloud to have it run fully managed, or connect your own AWS or GCP account and ZopDay sets it up there instead.

No credentials are prefilled. The Koyeb note in this README already explains why that matters, so the ZopDay note tells the user to set a real 32-character JWT_SECRET and states that the app stops at boot if they do not, rather than shipping a placeholder that looks usable.

How it differs from the existing eight

• Koyeb, Render, Railway, Sealos, CapRover, Fly.io and Dokploy run LibreDB Studio on that provider's own platform. DigitalOcean's Marketplace listing builds a Droplet inside the user's own DigitalOcean account.
• ZopDay can do the same via ZopCloud, or deploy into an AWS or GCP account the user already owns, so the Studio instance and its connection metadata sit on their own billing and inside their own IAM, VPC and data-residency rules. For a tool whose stated positioning is that it "deploys next to the data… nothing has to face outward", that is the case worth covering.
• ZopDay also supports Helm Charts into a Kubernetes cluster the user already runs, which lines up with the chart this repo already publishes.

So it complements the existing entries rather than duplicating any of them.

Deploy to ZopDay Button

Notes

• Helm Charts are supported only when deploying to the user's own cloud Kubernetes cluster, not ZopCloud.
• Using ZopDay requires a ZopDay account, the same as the other providers in this section.
• Translations are untouched, for the same reason docs(readme): add DigitalOcean Marketplace deploy button (#72) #230 and docs: add Sealos deployment option #296 left them alone: the translation-lag banner from docs: give every localized README a translation-lag banner, and a guard for it #1064 makes README.md authoritative, and the three invariants scripts/readme-check.mjs enforces are unaffected.
• Happy to add a distribution/channels.yaml entry (a kind: deploy-button in deploy-recipes, the same shape as koyeb-deploy-button) and a deploy/zopday/ directory if that would be useful — I left them out rather than guess at tier, pin and first_pr.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[cevheri]

Hi @muskanbandta23, Thanks for this contribution and welcome.
I have a question: is there a place to add this project to a templates page? If there is a spot where we can submit a PR (like Dokploy, caprover, rancher, etc.. for instance), let's do that as well. We find it more efficient to list libredb-studio in the template or marketplace sections of PaaS platforms; a setup that runs ready-made Docker images or Helm charts tends to be more robust and less prone to breaking. I am merging this PR now. Could you please look into the matter I mentioned above?

[cevheri]

interesting image:

[muskanbandta23]

@cevheri Sure. You can contribute the LibreDB Studio Helm chart to our ZopDev Helm Charts repository:

https://github.com/zopdev/helm-charts

We already have application charts there, so you can add LibreDB Studio as an application chart. Once you have the PR ready, we can review it from our side.

[cevheri]

Thanks @muskanbandta23, the chart is up: zopdev/helm-charts#322. It runs one pod with SQLite on a PVC, so it installs with default values. The lint workflow is waiting for a maintainer to approve the run, since this is our first PR there. Happy to adjust anything your reviewers flag.

[cevheri]

@cevheri Sure. You can contribute the LibreDB Studio Helm chart to our ZopDev Helm Charts repository:

https://github.com/zopdev/helm-charts

We already have application charts there, so you can add LibreDB Studio as an application chart. Once you have the PR ready, we can review it from our side.

Hi @muskanbandta23
zopdev/helm-charts#322 PR still open
is project deprecated or activly maintained, any update?