Self-host OrangeHRM with Levelrail

An open-source human resources management suite: PTO, recruitment, performance, and an employee directory.

  • Authororangehrm
  • LicenceGPL-3.0-or-later
  • Memory1 GiB
  • Services2

How to self-host OrangeHRM

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • mariadb:11
    • orangehrm/orangehrm:latest
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 5 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

OrangeHRM requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 not available
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0-or-later, 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.
  • Review. Image is not pinned to a version tag, so a redeploy can pull different code (orangehrm/orangehrm:latest).

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then OrangeHRM. 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 OrangeHRM docs page.

Deploy OrangeHRM your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy OrangeHRM from the CLI

levelrail-cli templates deploy orangehrm --name my-orangehrm

Deploy OrangeHRM with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/orangehrm/deploy

OrangeHRM configuration

OrangeHRM services

ServiceImagePortsVolumes
mariadb mariadb:11 none orangehrm_mariadb_data -> /var/lib/mysql
orangehrm orangehrm/orangehrm:latest 80 orangehrm_data -> /orangehrm

OrangeHRM environment variables

VariableServiceValue
MYSQL_DATABASE mariadb Preset by the template
MYSQL_PASSWORD mariadb Generated at deploy
MYSQL_ROOT_PASSWORD mariadb Generated at deploy
MYSQL_USER mariadb Preset by the template
ORANGEHRM_DATABASE_HOST orangehrm Preset by the template
ORANGEHRM_DATABASE_NAME orangehrm Preset by the template
ORANGEHRM_DATABASE_PASSWORD orangehrm Generated at deploy
ORANGEHRM_DATABASE_USER orangehrm Preset by the template

Ports and volumes

Ports
80
Volumes
2 named mounts: orangehrm_mariadb_data -> /var/lib/mysql, orangehrm_data -> /orangehrm

OrangeHRM FAQ

How much memory does OrangeHRM need?

The catalog lists about 1 GiB of memory for OrangeHRM across its 2 services.

Does OrangeHRM run on arm64?

For OrangeHRM, amd64 only, no arm64 image; amd64 is image published.

What licence is OrangeHRM under?

OrangeHRM is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.

Does OrangeHRM need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does OrangeHRM bundle?

The template includes MySQL, running as its own service.

Which ports does OrangeHRM use?

OrangeHRM listens on port 80 inside the stack.

Where does OrangeHRM keep its data?

In named volumes: orangehrm_mariadb_data mounted at /var/lib/mysql and orangehrm_data mounted at /orangehrm.

Can I deploy OrangeHRM on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for OrangeHRM, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image mariadb:11, orangehrm/orangehrm:latest is what you deploy there.

levelrail-cli templates deploy orangehrm --name my-orangehrm