Self-host Easy!Appointments with Levelrail
An open-source appointment scheduler for managing bookings, staff, and services.
- Authoralextselegidis
- LicenceGPL-3.0
- Memory512 MiB
- Archarm64
- Services2
How to self-host Easy!Appointments
-
Pull the images
2 images are pulled on your server.
Show images
alextselegidis/easyappointments:1.6.0mysql:8.4
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 5 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Easy!Appointments requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Easy!Appointments. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Easy!Appointments docs page.
Deploy Easy!Appointments your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Easy!Appointments from the CLI
levelrail-cli templates deploy easyappointments --name my-easyappointments Deploy Easy!Appointments with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/easyappointments/deploy Easy!Appointments configuration
Easy!Appointments services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| easyappointments | alextselegidis/easyappointments:1.6.0 | 80 | none |
| mysql | mysql:8.4 | none | easyappointments_mysql_data -> /var/lib/mysql |
Easy!Appointments environment variables
| Variable | Service | Value |
|---|---|---|
| BASE_URL | easyappointments | Preset by the template |
| DB_HOST | easyappointments | Preset by the template |
| DB_NAME | easyappointments | Preset by the template |
| DB_PASSWORD | easyappointments | Generated at deploy |
| DB_USERNAME | easyappointments | Preset by the template |
| MYSQL_DATABASE | mysql | Preset by the template |
| MYSQL_ROOT_PASSWORD | mysql | Generated at deploy |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: easyappointments_mysql_data -> /var/lib/mysql
Easy!Appointments FAQ
How much memory does Easy!Appointments need?
The catalog lists about 512 MiB of memory for Easy!Appointments across its 2 services.
Does Easy!Appointments run on arm64?
For Easy!Appointments, an arm64 image is published; amd64 is image published.
What licence is Easy!Appointments under?
Easy!Appointments is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Easy!Appointments need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Easy!Appointments bundle?
The template includes MySQL, running as its own service.
Which ports does Easy!Appointments use?
Easy!Appointments listens on port 80 inside the stack.
Where does Easy!Appointments keep its data?
In a named volume: easyappointments_mysql_data mounted at /var/lib/mysql.
Can I deploy Easy!Appointments on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id easyappointments for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image alextselegidis/easyappointments:1.6.0, mysql:8.4 is what you deploy there.