Skip to main content

​
Quick Start

This path uses the current development build reviewed for this documentation. It uses deploy/docker-compose.https.yml; docker-compose.platform.yml also contains defaults intended for development validation.

​
1. Clone the audited implementation

​
2. Prepare the environment

Do not expose the service with placeholder secrets from .env.example. The release installer detects missing or insecure release secrets and generates secure values where the current release flow supports it.

​
3. Use the production-style HTTPS stack

For a local/evaluation port pair that does not require host ports 80/443:
The HTTPS Compose file keeps PostgreSQL and the API off host-facing ports and exposes the browser entry point through the reverse proxy.

​
4. Verify the service

A healthy API returns a JSON object with status and database-index health information.

​
5. Sign in

Open:
For a fresh bootstrap with no GDC_SEED_ADMIN_PASSWORD, use:
You must change the password on first login.

​
6. Create the first managed objects

The current Stream Wizard selects an existing Connector. Create a Connector first under Connectors, then open Streams → Create First Stream. The current wizard flow is:
A successful first setup ends with a visible Stream and at least one Route/Destination configuration that can be monitored from Dashboard and Streams.
There is no current “register DataRelay Link” step because the audited source does not implement a Control↔Link management protocol.
Last modified on September 28, 2026