Skip to content

Adds ZopDay to the 1-Click cloud deployments - #2358

Closed
muskanbandta23 wants to merge 1 commit into
lissy93:masterfrom
muskanbandta23:docs-zopday-deploy
Closed

muskanbandta23 wants to merge 1 commit into
lissy93:masterfrom
muskanbandta23:docs-zopday-deploy

Conversation

@muskanbandta23

@muskanbandta23 muskanbandta23 commented Sep 24, 2026 •

Copy link
Copy Markdown

Adds one-click deployment with ZopDay to this list, alongside the existing options.

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.

Category

Docs

Overview

Adds ZopDay to the Deploy to the Cloud list, as a ninth 1-Click deployment option alongside Hostinger, Netlify, Vercel, Render, Railway, GCP, Easypanel and EdgeOne.

The existing entries all run Dashy on that provider's own platform. ZopDay can do that too, via ZopCloud, but it can also deploy into a cloud account the user already owns. Since Dashy is usually self-hosted alongside the services it links to, being able to put it in the same AWS, GCP or Azure account, on the same billing and behind the same network rules, is the part that is different here.

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

Issue Number

N/A

Additional Info

  • One line added to the existing list, using the same width="18" icon format as the entries around it.
  • 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 list.
  • Happy to add the matching entry to docs/deployment.md#deploy-to-cloud-service as well if you would like the two kept in sync.
  • AI disclaimer: this pull request was drafted with AI assistance, submitted on behalf of the ZopDay team.

Deploy to ZopDay Button

Deploy to ZopDay

@netlify

netlify Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for dashy-dev ready!

Name Link
🔨 Latest commit 8017619
🔍 Latest deploy log https://app.netlify.com/projects/dashy-dev/deploys/6ab4b98da44c66000815af94
😎 Deploy Preview https://deploy-preview-2358--dashy-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added the 📕 Docs [PR] Contains improvments or additions to documentation label Sep 24, 2026

@lissy93 lissy93 left a comment •

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @muskanbandta23, but I'm going to pass on this one.
For the 1-click options, I only add providers that Dashy users have asked for or that I've used myself. Nobody has requested ZopDay, and we already have easier ways to support AWS/GCP/Azure with our official image.

Seems like this PR is part of a mass-submission campaign you've got, where you've spammed tons of repos with the same ZopDay PR / undisclosed self-promotion. Please stop this.

@lissy93 lissy93 closed this Sep 24, 2026
@muskanbandta23

Copy link
Copy Markdown
Author

You're right, and I'm sorry.

This was part of a broad submission campaign across many repositories, and I should have said up front that I work on ZopDay instead of leaving you to work it out. Sending it without asking first, and without disclosure, was the wrong way to do this.

I'm closing the other open PRs now, and I won't submit to Dashy again. Thanks for saying it plainly rather than just closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📕 Docs [PR] Contains improvments or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants