docs: add ZopDay one-click deploy button to README

[muskanbandta23]

Description

Adds a ZopDay one-click deploy button to the badge row, alongside Zeabur, Vercel, Gitpod, and OpenDeploy.The button deploys NextChat's official Docker image on the port the app already uses.

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

• 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

Note: Helm Charts are supported only when deploying to the user's own cloud Kubernetes cluster, not ZopCloud

Why this is useful here

Getting your own instance running means choosing somewhere to host it and wiring it up first. This adds a single click from the README to a running instance.

It also covers the bring-your-own-cloud case: the same button can deploy into the user's own AWS, GCP or Azure account, so they own and bill the infrastructure directly rather than renting it from a platform.

How this fits with the existing options

The row already covers hosted platforms and a dev environment. ZopDay adds a path between them:

• Deploy to ZopCloud — fully managed, nothing to set up, like the Zeabur and Vercel entries.
• Deploy into your own AWS, GCP or Azure account — the instance runs in the user's own cloud, on their billing, under their own IAM, VPC and data-residency rules. Useful for teams who cannot put their conversations and API keys on a third-party platform.
• Helm Charts into a Kubernetes cluster the user already runs.

It also deploys the Docker image rather than building from the repo, so it does not need a fork.

Caveat

• OPENAI_API_KEY and CODE are still set by the user at deploy time, the same as with the existing options.
• Helm Charts can only be deployed to the user's own cloud Kubernetes cluster.
• This feature requires the user to have a ZopDay account.

Deploy to ZopDay Button

https://zop.dev/deploytozopday-inkhard.svg