From 2cb5e8ef4db303fdcf3e7fec818417bf72ad6c0e Mon Sep 17 00:00:00 2001 From: yangchuansheng Date: Tue, 12 May 2026 20:20:40 +0800 Subject: [PATCH 1/2] docs: add Sealos one-click deploy --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index f8943348fba..5f6457b2ac7 100644 --- a/README.md +++ b/README.md @@ -97,9 +97,13 @@ docker compose logs cap-web | --- | --- | | Docker Compose | VPS, home servers, and any Docker-capable host | | [Railway](https://railway.com/new/template/PwpGcf) | One-click managed hosting | +| [Sealos](https://sealos.io/products/app-store/cap) | One-click managed hosting with template-managed resources | | Coolify | Self-hosted PaaS deployments with `docker-compose.coolify.yml` | [![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/new/template/PwpGcf) +[![Deploy on Sealos](https://sealos.io/Deploy-on-Sealos.svg)](https://sealos.io/products/app-store/cap) + +The Sealos template is maintained in the Sealos templates repository at `template/cap/index.yaml`. Before deploying, review the optional `RESEND_API_KEY` and `RESEND_FROM_DOMAIN` inputs, plus the provisioned MySQL and object storage persistence settings. After deployment, open the generated Sealos app URL and complete Cap's first-run or login flow. For production, configure public URLs and replace the default secrets before exposing the deployment to the internet: From 5d02cb8549ddb9acd0f6298fc9dcfe68ad5bcdff Mon Sep 17 00:00:00 2001 From: yangchuansheng Date: Tue, 12 May 2026 20:25:34 +0800 Subject: [PATCH 2/2] docs: simplify Sealos deploy README entry --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 5f6457b2ac7..9ad2656ee35 100644 --- a/README.md +++ b/README.md @@ -103,7 +103,6 @@ docker compose logs cap-web [![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/new/template/PwpGcf) [![Deploy on Sealos](https://sealos.io/Deploy-on-Sealos.svg)](https://sealos.io/products/app-store/cap) -The Sealos template is maintained in the Sealos templates repository at `template/cap/index.yaml`. Before deploying, review the optional `RESEND_API_KEY` and `RESEND_FROM_DOMAIN` inputs, plus the provisioned MySQL and object storage persistence settings. After deployment, open the generated Sealos app URL and complete Cap's first-run or login flow. For production, configure public URLs and replace the default secrets before exposing the deployment to the internet: