Deploy Miniflux
Minimalist self-hosted RSS reader with PostgreSQL and a generated admin
Just deployed
Just deployed
/var/lib/postgresql/data
Deploy and Host Miniflux on Railway
Miniflux is a minimalist, open-source feed reader written in Go. It reads RSS, Atom and JSON Feed, removes trackers and ads from articles, and gives you a fast, keyboard-friendly web UI. It also has a REST API and supports the Fever and Google Reader APIs, so mobile and desktop apps can sync with it.
About Hosting Miniflux
This template deploys two services. Miniflux 2.3.5 builds from a public GitHub repo whose Dockerfile pins the official miniflux/miniflux image by version and digest, and Railway's PostgreSQL stores all Miniflux data on a volume. Miniflux has no files of its own, so a redeploy or restart loses nothing. The template asks you nothing: it generates the admin password and the media proxy key, runs database migrations on every start, sets the public URL and serves the web UI over HTTPS, with a /healthcheck health check. After deploy, open the URL and sign in as admin with the ADMIN_PASSWORD from the Miniflux service's Variables tab, then change it.
Common Use Cases
- A private, ad-free replacement for Feedly or Inoreader, with your reading history in your own database
- One sync backend for mobile and desktop feed apps through the Fever, Google Reader or Miniflux API
- Following blogs, release notes, YouTube channels and news sites, with filters, scraper rules and saved entries
Dependencies for Miniflux Hosting
- PostgreSQL (Railway's PostgreSQL service, included)
- A public HTTPS domain (Railway generates one)
Deployment Dependencies
- Miniflux source and releases: https://github.com/miniflux/v2/releases
- Configuration reference: https://miniflux.app/docs/configuration.html
- Template repo (Dockerfile, changelog): https://github.com/aalfath/miniflux-railway-template
Implementation Details
After the first login, change the password under Settings → Authentication. Miniflux creates the admin only while that user doesn't exist, so the generated ADMIN_PASSWORD never overwrites a password you changed. You can also delete the variable: the start script then skips admin creation.
Optional settings go on the Miniflux service as variables: POLLING_FREQUENCY and BATCH_SIZE (how often and how many feeds refresh), OAUTH2_PROVIDER with the other OAUTH2_* variables for OpenID Connect sign-in, and WORKER_POOL_SIZE if you follow many feeds.
Updates: the Miniflux service builds from the template repo. When the pinned version is bumped there, Railway shows an "update available" notice in your project, and you choose when to apply it. Read the repo's CHANGELOG.md first, and back up the Postgres volume before a major upgrade.
Why Deploy Miniflux on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Miniflux on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
