Forma LMS 4.1 on Ubuntu 24.04 on Azure User Guide
Overview
Forma LMS is the open source corporate Learning Management System, the community maintained fork of Docebo Community Edition. It delivers and tracks employee and customer training with a course catalogue and enrolments, SCORM, AICC and xAPI e-learning content, classroom and virtual sessions, learning plans, certifications, competency management, gamification and reporting across a multi tenant org chart. The cloudimg image ships Forma LMS 4.1 served by Apache over HTTPS with PHP 8.1 FPM on a hardened Ubuntu 24.04 LTS base, patched at build time, together with a bundled local MariaDB server so the appliance is complete and useful on its own. The web installer is pre completed and locked, and the installer and upgrade routes are disabled on the running image. No database and no shared password ship in the image: the first boot of every VM initialises its own database and generates a unique database password and a unique administrator password. The bundled MariaDB listens only on the loopback interface (127.0.0.1:3306). cloudimg's support team is on hand 24 hours a day by email (support@cloudimg.co.uk), with a guaranteed response within 24 hours.
What is included:
- Forma LMS 4.1 served by Apache over HTTPS (port 443, with port 80 redirecting to 443) and PHP 8.1 FPM, managed by systemd. PHP 8.1 is installed from the ondrej/php PPA because Forma LMS 4.1 supports PHP 8.0-8.1 only (Ubuntu 24.04 ships PHP 8.3); the PPA is restricted to PHP packages and stays enabled for PHP security updates
- A bundled MariaDB server, initialised on first boot with a database password unique to your instance
- The web installer pre completed and locked, and the installer and upgrade setup routes disabled on the running image
- A per VM administrator password generated on first boot and recorded in a root only file
- No database and no shared credentials in the image: each instance mints its own database and passwords on first boot
- A per instance HTTPS certificate generated on first boot (self-signed; regenerate for a DNS name with
formalms-set-hostname) - MariaDB bound to
127.0.0.1only, never exposed to the network - The cloud instance metadata endpoints blocked from the application services, and forwarded client-IP headers not trusted
- A systemd timer running Forma's scheduled jobs every five minutes
apache2.service,php8.1-fpm.serviceandmariadb.serviceas enabled systemd units- An unauthenticated
/healthzendpoint for Azure Load Balancer health probes - cloudimg's support team on hand 24 hours a day by email (support@cloudimg.co.uk), with a guaranteed response within 24 hours
Prerequisites
An active Azure subscription, an SSH key pair, and a VNet plus subnet in the target region. Standard_B2s (2 vCPU / 4 GiB RAM) is a sensible starting point for a small team; step up to a larger size for heavier concurrent use. NSG inbound: allow 443/tcp for the application (HTTPS, primary), 80/tcp (which redirects to 443), and 22/tcp from your management network. The bundled MariaDB is never exposed: it listens on 127.0.0.1 only, so port 3306 stays off the network.
Step 1 - Deploy from the Azure Marketplace
Sign in to the Azure Portal, choose Create a resource, search the Marketplace for Forma LMS by cloudimg, and select Create. On Basics pick your subscription, resource group, region and size; under Administrator account choose SSH public key and paste your key; under Inbound port rules allow SSH (22), HTTP (80) and HTTPS (443). Then Review + create then Create.
Step 2 - Deploy from the Azure CLI
# Accept the Marketplace terms once per subscription (required before the first CLI deploy)
az vm image terms accept --urn cloudimg1647283583153:formalms-ubuntu-24-04:default:latest
az vm create \
--resource-group <your-rg> \
--name formalms \
--image cloudimg1647283583153:formalms-ubuntu-24-04:default:latest \
--size Standard_B2s \
--admin-username azureuser \
--generate-ssh-keys \
--public-ip-sku Standard
Then open ports 80 and 443:
az vm open-port --resource-group <your-rg> --name formalms --port 80,443
Step 3 - Confirm the services are running
SSH in as azureuser and confirm Apache, PHP FPM, MariaDB and the first boot service are all active. Note that MariaDB listens only on 127.0.0.1:3306 while Apache serves Forma over HTTPS on port 443 (port 80 redirects to 443), and the unauthenticated /healthz endpoint answers 200 for load balancer probes.
systemctl is-active apache2 php8.1-fpm mariadb formalms-firstboot
curl -s -o /dev/null -w 'healthz -> %{http_code}\n' http://127.0.0.1/healthz
Expected output:
active
active
active
active
healthz -> 200

Step 4 - Retrieve the per VM administrator password
On the first boot of every instance, a one shot service generates a unique administrator password and a unique MariaDB password and writes them to /root/formalms-credentials.txt, readable only by root. There is no shared default login.
sudo cat /root/formalms-credentials.txt
The file lists the admin login (admin), the generated password, the application URL and the loopback MariaDB details. The keys are shown below; the values are unique to your instance.
FORMALMS_URL=https://<your-instance-ip>/
FORMALMS_ADMIN_USER=admin
FORMALMS_ADMIN_PASSWORD=<FORMALMS_ADMIN_PASSWORD>
FORMALMS_DB_NAME=forma
FORMALMS_DB_USER=formauser
FORMALMS_DB_PASSWORD=...

Step 5 - Sign in to Forma LMS
Browse to https://<your-instance-ip>/ and sign in with the username admin and the password from the credentials file. The certificate is self-signed and generated for your instance, so your browser shows a one time warning; to serve a DNS name with a matching certificate run sudo formalms-set-hostname <your-dns-name>. The login form posts your credentials over Forma's own authentication and lands you in the platform.

After signing in, switch to the Admin area to reach the administration dashboard. It summarises registered users, super administrators, online users, the installed version and course and access statistics.

Step 6 - Manage courses
From the E-learning menu open the course management list. Here you create course categories and courses, import SCORM, AICC and xAPI content, enrol learners, and run classroom and virtual sessions. A fresh appliance starts with an empty course list ready for your content.

Step 7 - Manage users
From the Users menu open user management to create users and groups, assign administrator and instructor roles, import users in bulk, and organise your learners across the org chart.

Security model
This image never ships a usable default login and never ships a database. On the first boot of every VM a fresh database is initialised and a unique administrator password and a unique MariaDB password are generated and written to the root only credentials file, so no two deployments share a password. You can prove the model on the instance: the per VM administrator authenticates through the real Forma login form, while a blank password and common weak guesses are rejected.
sudo bash /usr/local/sbin/formalms-cred-roundtrip.sh
Expected output:
OK admin authenticates; blank+weak rejected
Additional hardening in this image:
- Setup routes disabled once installed. The web installer is completed and locked, and Forma's installer and upgrade setup routes are refused on the running image (they return
403), closing a class of unauthenticated administrator reset through those routes. The read-only system status route stays available. - HTTPS from first boot with a per instance certificate; port 80 redirects to 443. Forwarded client-IP headers (
X-Forwarded-For,X-Real-IP) are stripped at the web server, so the application only ever sees the real peer address. - No shared database state. The schema ships as a seed that is imported into a freshly initialised database on first boot; nothing in the image carries a usable password.
- Cloud metadata endpoints blocked from the application services (MariaDB, PHP FPM, Apache and the first boot and cron units), while the Azure agent and cloud-init keep the access they need.
- Dependencies patched. The Symfony libraries are updated to their advisory-fixed releases. One residual advisory remains in the Twig 2.x templating library that Forma requires (Forma pins the 2.x line, which has no fixed release): it is not reachable in this image, because Forma loads only its own shipped templates from the filesystem, with no template sandbox and no user-supplied template source. It is documented here rather than suppressed.

Versions and the first boot service
Confirm the installed component versions, the completed and locked install, and the first boot service.
php8.1 -v | head -1
mariadb --version
systemctl is-active formalms-firstboot

Where your data lives
The Forma LMS application code lives at /var/www/formalms/html, its configuration at /var/www/formalms/html/config.php (denied to the web by Forma's own rules), and uploaded and generated content under /var/www/formalms/html/files. No database ships in the image: the MariaDB datadir under /var/lib/mysql is empty until first boot, where it is initialised and the forma database is created from the shipped schema seed with a password unique to your instance. The database is reachable only on the loopback interface. The formalms-cron.timer systemd timer runs Forma's scheduled jobs every five minutes.
Support
cloudimg's support team is on hand 24 hours a day by email (support@cloudimg.co.uk), with a guaranteed response within 24 hours. Contact support@cloudimg.co.uk for deployment guidance, course and SCORM configuration, learning plan and certification setup, version upgrades, performance tuning and MariaDB database administration.