Two turnkey FeedLand deployments — Docker Compose and Cloudron

[rmdes]

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

[scripting]

@rmdes -- thanks for posting this here, great comments and the work is appreciated. If Scott says it's good, then of course we will use this to make it even easier for the next people to come along.

[scotthansonde]

@scripting This is great! We can go ahead and link to it.

@rmdes I'm really happy you've built on the original project and made improvements. I'll certainly try it out, and look for good ideas I can steal adopt for my repo. I really like the idea of the mail catcher. That really simplifies getting the first user set up.

[rmdes]

Thanks both, this made my day. 🙏

@scotthansonde please do steal the mail catcher, that's exactly the spirit. It's a tiny addition: a mailpit service (axllent/mailpit) with MP_WEBROOT=/mail, FeedLand's smtpHost/smtpPort pointed at mailpit:1025, and one Caddy route — handle /mail* → reverse_proxy mailpit:8025.

A new user signs up, the confirmation email gets caught by Mailpit, and they click the link at /mail. No SES/SMTP to configure and no querying the DB for the magic string to get that first account going — and when someone's ready for real delivery they just set the SMTP vars in .env.