Easy!Appointments
Community2 services
Easy!Appointments, the open-source appointment scheduler — booking pages, working hours, provider calendars, Google Calendar sync — with a dedicated MySQL database.
What you get
- All 2 services provisioned together: easyappointments, easyappointments-db
- A community template, not yet verified end to end by the Railyard team
- Automatic HTTPS and zero-downtime deploys
How to deploy Easy!Appointments
- 1
Connect a server
Attach a DigitalOcean, Hetzner or Vultr server to Railyard, or any Linux box over SSH.
- 2
Click "Deploy Easy!Appointments"
Railyard builds the container and provisions all 2 services.
- 3
Set your domain
Point your domain at the app. Railyard issues an HTTPS certificate and keeps it renewed automatically.
Why deploy on Railyard
Railyard provisions all 2 services in this stack together — easyappointments, easyappointments-db — wired to reach each other over the private network, on a server you already pay for.
Deploying Easy!Appointments is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A public booking page for a salon, clinic or any service business with multiple providers
- Pairing with Google Calendar sync so bookings show up where staff already look
Good to know
- DB_USERNAME is set to root, not a dedicated app user — confirmed from the image's own published Docker Hub documentation, which connects as root by default rather than a scoped account; this is the upstream image's own design, not a Railyard simplification
- No app-level volume — Easy!Appointments keeps no persistent state outside its database
- No SMTP is configured — appointment confirmation/reminder emails won't send until the MAIL_SMTP_* env vars are added