Deploy Rallly
Self-hosted Doodle alternative: meeting polls, pinned 4.17.1, Postgres
Just deployed
Just deployed
/var/lib/postgresql/data
Deploy and Host Rallly on Railway
Rallly is an open-source (AGPL-3.0) scheduling tool and a self-hosted alternative to Doodle. You create a meeting poll with a few candidate dates and times, share the link, and participants mark which ones work for them, without needing an account. You then pick the best slot and finalise the meeting.
About Hosting Rallly
This template deploys Rallly 4.17.1 from the official lukevella/rallly image, pinned by version and digest and built from a public GitHub repo, together with Railway's Postgres on a volume. All polls, users and settings live in Postgres, so they survive redeploys and restarts. The session key and database password are generated for each deployment, and the public URL comes from the Railway domain. The only prompt is your email (INITIAL_ADMIN_EMAIL). Rallly signs users in with an emailed code: until you add SMTP settings, the template prints each email to the Rallly service's deploy logs, which only members of your Railway project can read.
Common Use Cases
- Find a meeting time across a team, a club or several companies without back-and-forth emails
- Run a private, self-hosted Doodle replacement where poll data stays in your own database
- Let people vote on dates for events, interviews or classes from a single shared link
Dependencies for Rallly Hosting
- Rallly web app (built from aalfath/rallly-railway-template)
- PostgreSQL (Railway's Postgres, with a volume)
Deployment Dependencies
- Rallly source and releases: https://github.com/lukevella/rallly/releases
- Self-hosting configuration reference: https://support.rallly.co/self-hosting/configuration
- Official Docker image: https://hub.docker.com/r/lukevella/rallly
Implementation Details
After the deploy is green:
- Open the Rallly domain and sign up with the email you entered as
INITIAL_ADMIN_EMAIL. - In Railway, open the Rallly service, then Deployments, View logs, find
===== EMAILand enter the 6-digit code. - Go to
/control-paneland click "Make me an admin". - Before you invite others, add SMTP variables on the Rallly service:
SMTP_HOST,SMTP_PORT,SMTP_SECURE(truefor port 465),SMTP_USER,SMTP_PWD,NOREPLY_EMAIL. SettingSMTP_HOSTswitches off the log output.
Optional: restrict sign-ups with ALLOWED_EMAILS=*@example.com or REGISTRATION_ENABLED=false, add single sign-on with the OIDC_* variables, and for a custom domain set NEXT_PUBLIC_BASE_URL=https://YOUR-DOMAIN. Image uploads (profile pictures, logos) need an S3-compatible bucket (S3_* variables); everything else works without one.
Updates: the Rallly service builds from the GitHub repo, so Railway shows you an update when we bump the pinned version there. Each change is listed in the repo's CHANGELOG.md, breaking changes first. Rallly runs its database migrations on start; back up the Postgres volume before a major upgrade.
Why Deploy Rallly 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 Rallly 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
INITIAL_ADMIN_EMAIL
Your email. Sign up with it, then claim the admin role at /control-panel.
