Liferay Docker Manager (LDM) Showcase¶

Seeing is believing. Check out these short demonstrations of Liferay Docker Manager in action to see how it can accelerate your development workflow.

🚀 Fast Provisioning¶

Watch how quickly LDM provisions a fully functional Liferay environment, complete with SSL, automatic host file mapping, and an instant fast login token generation.

https://github.com/user-attachments/assets/8266af0f-f7a4-4040-91b1-f41cf2a28b39

Transcript: Fast Provisioning¶

The user executes ldm run ldm-demo --fast-login --ssl to provision a new environment.
LDM interactively prompts for the virtual hostname, defaulting to ldm.demo.
Missing host entries are detected, and LDM automatically adds ldm.demo to the /etc/hosts file (requesting sudo permissions).
The user selects the Liferay release version (e.g., 2026.q1.7-lts).
LDM downloads the pre-warmed database seed for this version.
The project is bootstrapped directly from the seed, instantly hydrating the local volumes with pre-configured OSGi state and data.
Local SSL certificates are generated for ldm.demo using mkcert.
The Docker Compose stack is started, and LDM tails the logs until the server is healthy.
The instance becomes accessible at https://ldm.demo, where the user logs in and easily creates a new site using a template.

📸 Snapshots & Restoration¶

Accidentally broke your environment? Watch how easy it is to list existing database and volume snapshots, and instantly roll back to a known good state.

https://github.com/user-attachments/assets/7322c675-2c23-4f61-b0f2-f1d169e8a951

Transcript: Snapshots & Restoration¶

The user executes ldm restore ldm-demo --list to view all available local snapshots for the project.
LDM displays the available snapshots, revealing a "gold-standard-demo" snapshot at index [1].
The user initiates the rollback by executing ldm restore ldm-demo --index 1.
LDM safely tears down the currently running ldm-demo stack and cleans all corrupted data, logs, and state.
The snapshot's integrity is verified before the restoration begins.
Local volumes are hydrated from the snapshot archive, and an orchestrated database restore is triggered.
Once the database is successfully restored, LDM prompts the user to restart the project.
The infrastructure and Liferay containers spin back up.
The environment is fully reverted, allowing the user to browse the restored site exactly as it was when the snapshot was captured.

☁️ Cloud Hydration¶

See how seamlessly LDM pulls backups directly from Liferay Cloud environments (like prd or uat) and restores them locally, giving you an exact replica for debugging.

https://github.com/user-attachments/assets/3bf7e8e6-6740-4a6c-a350-28e44c9d5bde

Transcript: Cloud Hydration¶

The user executes ldm --cloud-project lctmodernintranetpsql --host-name intranet.demo --hydrate-from prd --no-env-sync.
LDM scans the cloud workspace and automatically fetches the latest database and volume backups from the production (prd) environment.
The backups are downloaded and organized into local snapshots, with PostgreSQL automatically detected as the database type.
LDM triggers a local restore, tearing down any existing stack and scaffolding the Docker environment.
Cloud data volumes are unpacked and internal Docker volumes are hydrated.
The cloud database dump is decompressed and scrubbed of any cloud-specific meta-commands.
An orchestrated database restore wipes the existing local schema and securely imports the production data.
Virtual host entries are synchronized to intranet.demo.
The environment starts up, and the user can browse their locally running, exact replica of the production Intranet site at https://intranet.demo.

⚡ OSGi State Persistence¶

Minimize boot times on local development environments by persisting the OSGi bundle resolution state across container lifetimes.

See the OSGi State Persistence Performance Showcase for timing comparisons, speed improvement metrics, and architectural details.

Last Updated: 2026-08-05 | Last Reviewed: 2026-07-02