Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Two turnkey FeedLand deployments — Docker Compose and Cloudron

Open Beginner friendly
#75 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, docker-compose, mysql
Domain
documentation

Research direction

Start with the repository’s install documentation and inspect how the existing HTTPS guide is linked. Review the two referenced deployment repositories, then add suitable links for the Docker Compose and Cloudron options. Done means both deployment paths are clearly presented without disrupting the existing installation guidance.

Written by the indexing model from the issue text.

Description

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.

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-dockerdocker 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

Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/feedlandInstall

All issues in scripting/feedlandInstall

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.