Deploy wallabag
Read-it-later app (Pocket alternative) with Postgres and Redis imports
Just deployed
/data
Just deployed
/var/lib/postgresql/data
Redis
Just deployed
/data
Deploy and Host wallabag on Railway
wallabag is an open-source (MIT) read-it-later app. Save any web page and wallabag keeps a clean, readable copy of the article, with tags, annotations, full-text search and exports (EPUB, PDF and more). It has Android and iOS apps, browser extensions and e-reader support, and imports from Pocket, Instapaper, Omnivore and others.
About Hosting wallabag
wallabag is a PHP (Symfony) app served by nginx and PHP-FPM. It needs a SQL database, a writable folder for article images, and a queue with a worker for large imports. This template deploys wallabag 2.6.18 from the official image with Railway Postgres and Railway Redis on the private network. On the first deploy it installs the database and creates your admin account with a generated password, so the well-known wallabag / wallabag login never works. Later deploys run the database migrations. Imports run in the background through Redis. Article images and sessions are stored on a volume, so they survive redeploys.
Common Use Cases
- Replace Pocket or Omnivore: import your export and keep reading on your own server
- Save articles from your phone or browser and read them later on a Kobo, KOReader or any e-reader
- Keep a searchable, tagged archive of everything you've read, with annotations
Dependencies for wallabag Hosting
- PostgreSQL: users, articles, tags and settings (Railway Postgres, included)
- Redis: background import queue (Railway Redis, included)
Deployment Dependencies
- wallabag: GitHub, 2.6.18 release, documentation
- Official Docker image: wallabag/docker
- Template source: aalfath/wallabag-railway-template
Implementation Details
The template deploys three services:
| Service | What it does | Storage |
|---|---|---|
| wallabag | Web app (nginx + PHP-FPM) and the Redis import worker, built from the template repo | Volume at /data (article images, sessions) |
| Postgres | Database | Volume |
| Redis | Import queue | Volume |
After deploy:
- Open the wallabag service's public URL.
- Log in as
adminwith theADMIN_PASSWORDshown in the wallabag service's Variables tab. Change it under Config → Password, and set your email under Config → User information. - For the mobile apps, create an API client under Developer → Create a new client.
Optional variables you can add to the wallabag service:
SYMFONY__ENV__MAILER_DSN, for examplesmtp://USER:PASSWORD@smtp.example.com:587, plusSYMFONY__ENV__FROM_EMAIL(email is off by default)SYMFONY__ENV__FOSUSER_REGISTRATION=trueto allow public sign-up (needs email)- With a custom domain, set
SYMFONY__ENV__DOMAIN_NAMEtohttps://YOUR-DOMAIN
Updates: the wallabag service builds from the template's GitHub repo. When a new wallabag version is added there, Railway shows an "update available" notice on your project, and you choose when to apply it. Read the repo's CHANGELOG first. Migrations run on the next start.
Why Deploy wallabag 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 wallabag 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
