Explanation¶
You want to understand why. These pages explain LDM's design and the reasoning behind its defaults. Nothing here is a set of steps to follow — for that, see the How-to guides or Reference.
How LDM is put together¶
- Architecture — the container topology, volume strategy and how the pieces fit.
- Remote Node Architecture — how a command finds the right machine, and how target resolution works.
- Permissions & the Reclaim Helper — why
short-lived Alpine containers appear during a run, which directories they
change, and why the mode is
777.
What LDM gives you out of the box¶
- Key Features — the capabilities LDM provides without being asked: session isolation, zero-config SSL, snapshots, fail-fast checks.
The two cascades — which one do you want?¶
LDM layers two different things, and both are commonly called a "hierarchy". They are unrelated, and picking the wrong one wastes a reader's time:
- Conventions & Configuration — the default
stack (which database, which search mode, which ports) and how an LDM
setting is resolved, from a command-line flag down to the built-in
convention. Pick this if your question is about an LDM flag or default,
such as
--dbordatabase_mode. - Properties Cascade & Override Hierarchy — how
portal-ext.propertiesfiles are merged, from the pre-warmed seed up to your project's own customisations. Pick this if your question is about a Liferay property.
Everything else¶
- Internationalization & Transcoding — how non-ASCII project names become safe container, volume and host identifiers.
- FAQ & Walkthroughs — common questions, with worked answers.
Last Updated: 2026-10-16 | Last Reviewed: 2026-10-16