Deploy Password Pusher
Share passwords, files and URLs via links that expire. Postgres included.
Password Pusher
Just deployed
/opt/PasswordPusher/storage
Just deployed
/var/lib/postgresql/data
Deploy and Host Password Pusher on Railway
Password Pusher (pwpush) is an open-source app for sharing passwords, text, files, URLs and QR codes through links that expire after a set number of days or views. Payloads are encrypted at rest, and every view is recorded in an audit log. It offers a web UI and a JSON API.
About Hosting Password Pusher
This template runs Password Pusher 2.17.4 from the official pglombardo/pwpush image, pinned by version and digest, built through the repository aalfath/password-pusher-railway-template. It has two services. The app service runs the web server and the background worker that expires and purges pushes. A Railway PostgreSQL service holds users, encrypted pushes, audit logs and the job queue. Uploaded files go on a volume. The deploy form asks for nothing. Railway generates the encryption key, the Rails secret and a one-time boot code for the first admin account. Database migrations run on every start. The app runs within Railway's 0.5 GB per-service memory limit.
Common Use Cases
- Send a password, API key or recovery code to a colleague or customer with a link that expires after one view or a few days
- Share sensitive files and URLs without leaving copies in chat or e-mail history
- Run an internal, self-hosted alternative to pwpush.com, with an audit log of who viewed each push and when
Dependencies for Password Pusher Hosting
- PostgreSQL (Railway's PostgreSQL service, included)
- A Railway volume for uploaded files (included)
Deployment Dependencies
- Password Pusher source and releases: https://github.com/pglombardo/PasswordPusher (v2.17.4)
- Self-hosted configuration reference: https://docs.pwpush.com/docs/self-hosted-configuration/
- Template repository: https://github.com/aalfath/password-pusher-railway-template
Implementation Details
Services:
Password Pusher: the public web app and API on port 5100 (Thruster in front of Puma), plus the Solid Queue worker in the same container. Volume at/opt/PasswordPusher/storage. Health check/up.Postgres: Railway's PostgreSQL, private network only, on its own volume.
After deploy:
- Open the app's URL. The first visit goes to
/first_run. - Copy
PWP_FIRST_RUN_BOOT_CODEfrom the Password Pusher service's Variables tab, and use it to create the administrator account. - Anyone can create pushes without an account (upstream default). Set
PWP__ALLOW_ANONYMOUS=falseto require a login, andPWP__DISABLE_SIGNUPS=trueto stop new sign-ups.
Optional: SMTP for account e-mails and password resets (PWP__MAIL__SMTP_ADDRESS, PWP__MAIL__SMTP_USER_NAME, PWP__MAIL__SMTP_PASSWORD, then PWP__ENABLE_USER_ACCOUNT_EMAILS=true). If you add a custom domain, set PWP__HOST_DOMAIN to it. Never change PWPUSH_MASTER_KEY once pushes exist, or they become unreadable.
Updates: the app service builds from the template repository. When it moves to a new Password Pusher release, Railway shows you an update notice. Read CHANGELOG.md, then apply it. Migrations run automatically.
Why Deploy Password Pusher 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 Password Pusher 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
Password Pusher
aalfath/password-pusher-railway-template
