Skip to main content

Testing environment

This testing environment lets you validate the Hublot application in conditions close to production, with OIDC authentication and real-time services. It is intended for functional tests and demos; it is not designed for load performance, benchmarks, or sensitive data. It will be available at https://forge.hublot.cloud/hublot/hublot-testing-demo.

Scope​

Allows:

  • Test the UI and user journeys
  • Test authentication via Logto (OIDC)
  • Test real-time flows via LiveKit

Does not allow:

  • Load or performance tests
  • Personal or sensitive data
  • SLA or high availability

Prerequisites​

  • Docker
  • Docker Compose (included with Docker Desktop)
  • mkcert

Clone the repository​

git clone https://forge.hublot.cloud/hublot/hublot-testing-demo
cd hublot-testing-demo

Quick start​

  1. Copy the sample environment file and set the host machine IP:

    cp .env.sample .env

    Edit .env and set HOST_IP (do not use 127.0.0.1, required by LiveKit and the reverse proxy).

  2. Add local domains to the hosts file (do not use 127.0.0.1):

    <HOST_IP> app.hublot.local
    <HOST_IP> auth.hublot.local
    <HOST_IP> auth-admin.hublot.local
    <HOST_IP> livekit.hublot.local

  3. Install mkcert and generate local certificates:

    mkcert -cert-file certs/localhost.pem -key-file certs/localhost-key.pem \
      app.hublot.local auth.hublot.local auth-admin.hublot.local livekit.hublot.local

  4. Start the stack:

    docker compose up

Services and URLs​

Default accounts (Logto)​

  • Admin: admin / hublotlogto

  • Demo users:

    • demo1 / demohublot
    • demo2 / demohublot

Reset data​

To clear local volumes and reset the stack state:

./reset.sh

Notes​

  • Use the host machine IP in HOST_IP and in the hosts file; 127.0.0.1 will be misinterpreted inside containers.