docs: add ZopDay to the deploy options - #740

Adds one-click deployment with ZopDay to the Deploy section, alongside the Netlify, Vercel and Cloudflare entries. README only, +6/−0.

Disclosure up front: I work on ZopDay. This project is MIT and the section already carries three providers, so this is offered as an addition rather than a replacement for any of them.

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 open a shareable deploy link and deploy with one click. The link can also carry preset environment variables so required configuration fills in automatically. Try it out: https://zop.dev/zopday/app/deploy

One-Click Deploy with ZopDay: https://zop.dev/zopday/oss

What changed

One #### Deploy to ZopDay entry after Cloudflare, in the same heading / one-sentence / button shape as the three above it. Nothing else is touched.

What it offers

It is the Dockerfile already in this repository, as a button. The link builds that file — npm run build, then the dist/ output copied into nginx:stable-alpine with your nginx/nginx.conf — and runs it on port 8080, matching your EXPOSE 8080 and the 8080:8080 mapping in docker-compose.yml.

That path currently works but is not mentioned anywhere in the README, so anyone who wants the containerised option has to find the Dockerfile, docker-compose.yml and nginx/ directory themselves.

No environment variables are involved: the build is static, the deploy link carries only the repository URL and the port, and nothing is preset.

How it differs from the existing three

• Netlify, Vercel and Cloudflare publish dist/ to a CDN. For most people deploying a static Astro site that is the better answer, and this does not try to displace it — the entry is placed last for that reason.
• ZopDay instead runs the container this repo already defines, which is useful in one specific case: teams who have to deploy into an AWS, GCP or Azure account they own — for an internal site, or because everything else they run is already there. The same nginx image can also go to a Kubernetes cluster they already run, via Helm.

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

Deploy to ZopDay Button

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

Notes

• The badge is 165×32, in line with the Netlify button (179×32) and the Vercel button (103×32). Each button sits on its own line here, so no size attribute is needed.
• The badge is served from the production host zop.dev, so it will not break later.
• npm run check passes locally on this branch — including prettier --check ., which covers README.md.
• 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 three options in this section.
• Happy to adjust the wording or placement, or to fold it into a more general "Docker" entry instead if you would rather document the container path without naming a provider.