Start IAS

Start IAS

IAS stands for Idelium Administration Server. In the Docker stack it is provided by Idelium Web, Idelium API, MariaDB, and an initialization container that runs database setup before the API becomes available.

Recommended demo quickstart

Use the quickstart wrapper for a local evaluation. It prepares the environment, configures the demo administrator, starts the Docker stack in demo mode, and prints the local URL:

cd idelium-docker
./quickstart-demo.sh

The wrapper performs the following actions:

1. Verifies that the required sibling repositories are available.
2. Creates .env from .env.example when the file is missing.
3. Writes the local demo administrator credentials to ignored secret files.
4. Builds MariaDB, API, and frontend images from the local checkouts.
5. Starts MariaDB and waits for its health check.
6. Runs migrations and demo seed data through ideliuminit.
7. Starts the API and frontend only after dependencies are ready.
8. Runs an HTTPS smoke test through the frontend reverse proxy.

Open the interface at:

https://localhost

If HTTPS_PORT is set in .env, open that port instead.

Demo mode generates a local self-signed TLS certificate. Your browser may show a certificate warning the first time you open the page. Accept it only for this local development URL.

Sign in to the demo portal

After ./quickstart-demo.sh completes, sign in with the local demo administrator:

Email: admin@idelium.org
Password: admin

These credentials are intended only for local demo mode. Do not reuse them in production or in shared environments.

The quickstart writes the same values to:

secrets/admin_email
secrets/admin_password

If you had already started the demo before this default administrator was configured, reset the local database volume and run the quickstart again:

docker compose -f docker-compose.yml -f compose.demo.yml down --volumes
./quickstart-demo.sh

Removing volumes is destructive for the local demo database. Use it only when you intentionally want a clean local environment.

Demo identities

The stack also creates an additional generated demo identity for test execution and sample flows. Read it from the ignored secret files only when you need it:

secrets/demo_email
secrets/demo_password

Keep those values private. Do not add them to screenshots, issue comments, logs, or documentation.

Production-oriented local mode

Use production mode when testing the stack with real secret files and a trusted certificate:

./start-idelium.sh --production

Production mode builds local images, requires mounted secret files, requires a trusted certificate, and does not enable demo seed data.

Release mode

Use release mode when the deployment must pull immutable published images rather than build from adjacent source checkouts:

./start-idelium.sh --release

Release mode should be used only with reviewed image references and matching configuration.

Stop the stack

Stop demo containers while keeping database and certificate volumes:

docker compose -f docker-compose.yml -f compose.demo.yml down

Remove demo volumes when you intentionally want a clean database and certificate:

docker compose -f docker-compose.yml -f compose.demo.yml down --volumes

Removing volumes is destructive. Secret files under secrets/ remain on disk until you rotate or remove them intentionally.

Troubleshooting startup

If startup fails, inspect the initialization service first:

docker compose ps
docker compose logs --tail=100 ideliuminit
docker compose logs --tail=100 ideliumapi
docker compose logs --tail=100 ideliumfe

The API is intentionally blocked until initialization completes successfully.