Access TestGen from Another Machine¶
Configure TestGen so that users, AI clients, and integrations can reach it from machines other than the TestGen server. By default, TestGen expects to be reached at localhost.
Set the base URLs¶
Set these variables to the URLs at which other machines reach TestGen, using the https scheme if TestGen is served over HTTPS.
| Variable | Default | Purpose |
|---|---|---|
TG_UI_BASE_URL |
http://localhost:8501 |
The UI URL, used in links in email notifications and PDF reports. |
TG_BASE_URL |
http://localhost:8530 |
The API and MCP server URL. Required for AI clients and OAuth clients on other machines. |
-
Navigate to the directory that contains the
docker-compose.ymlfile for TestGen.- If the instance was installed using dk-installer.exe, the file can be located under "AppData\Local\DataKitchenApps".
- If the instance was installed using dk-installer, the file can be located in the folder from which the Python installer was executed.
-
Add the following lines under the x-common-variables section, using the host ports from the engine service's
portssection. -
Restart the application.
-
Open the
~/.testgen/config.envfile in a text editor. -
Add the following lines (one variable per line, no quotes).
-
Restart the application. Stop the running TestGen process with Ctrl+C in the terminal where it is running, then start it again.
Open the ports¶
On a Docker or pip install, open the UI port and the API and MCP port, 8501 and 8530 by default, in the firewall or security group of the TestGen server. On Kubernetes, the ingress publishes both.