Home

Idelium Docker wiki

Welcome to the Idelium Docker wiki. This documentation explains how to run the Idelium test automation platform from the Docker stack, how the services fit together, and how to execute a first Selenium or Postman-based cycle.

Idelium is composed of:

• Idelium Web, the browser-based administration interface.
• Idelium API, the Laravel backend for authentication, configuration, projects, tests, cycles, and results.
• Idelium CLI, the execution agent used to run Selenium, Appium, Postman, and plugin-based steps.
• Idelium Docker, the reproducible local and release deployment topology.

Start here

1. Read Pre-requisite to prepare Docker, Git, OpenSSL, and the required sibling repositories.
2. Read Architecture to understand the enterprise topology and data flow.
3. Follow Start IAS to start the Idelium Administration Server.
4. Run a first browser scenario with Quick Start Selenium.
5. Run a first API scenario with Quick Start Test API Using Postman.

Security model for this wiki

The Docker stack no longer documents fixed demo passwords. Demo and administrator identities are generated locally under the ignored secrets/ directory when ./start-idelium.sh --demo is used. Do not paste generated passwords, API keys, session identifiers, private keys, or complete authorization headers into wiki pages, issues, screenshots, or support messages.

Repository layout expected by the stack

For local builds, keep the three application repositories as siblings:

workspace/
├── idelium-api/
├── idelium-docker/
└── idelium-web/

The Docker stack reads the adjacent API and Web checkouts, labels built images with source revisions, runs migrations through a one-shot initialization container, and exposes only the HTTPS frontend to the host.