Two turnkey FeedLand deployments — Docker Compose and Cloudron

从仓库的安装文档开始，检查现有 HTTPS 指南的链接方式。查看所引用的两个部署仓库，然后为 Docker Compose 和 Cloudron 选项添加合适的链接。完成的标准是清晰呈现这两种部署路径，同时不影响现有的安装指南。

Hi Dave,

I'm a self-hoster who's been running my own FeedLand instance, and along the way I hit the usual rough edges of getting it stood up and keeping it running. So I built two ways to make that a single command, and I wanted to share them here in case they're useful to other people setting up their own instances.

• feedland-docker — a Docker Compose deployment
• feedland-cloudron — a Cloudron app package

Neither is from scratch. The Docker one started from Scott Hanson's feedlandDockerCompose and leans on the Caddy setup from Scott's https.md guide in this repo. I just kept tightening it for an always-on server.

feedland-docker — docker compose up -d and you get FeedLand, MySQL, and Caddy with automatic HTTPS. A few things I added for running it unattended:

• Only Caddy is exposed to the net; the app and database stay on internal networks
• Healthchecks so services come up in the right order and restart cleanly
• A built-in mail catcher, so email confirmation works out of the box before you've wired up SES or SMTP
• Backup and migrate scripts

feedland-cloudron — for folks on Cloudron, it's an install away. Pre-built images, and Cloudron's managed addons handle MySQL, outbound email, and HTTPS for you:

cloudron install --image rmdes/feedland-cloudron:latest --location feedland.example.com

My question: would you consider linking these from the install docs, the way Scott's HTTPS guide is linked? I'm happy to maintain them and adjust anything to fit how you'd want easy deployment presented. And of course happy to hear if you'd rather they live somewhere else entirely.

Tutorial on how to self-host feedland

Thanks for FeedLand — it's a genuinely nice thing to run. ;-)

— rmdes