Skip to content

Read Default Connection settings from .env and .env.local - #2612

Open
kmcginnes wants to merge 1 commit into
t3/typescript-startup-stack-7-fetch-timeout-expansion-limitfrom
t3/typescript-startup-stack
Open

kmcginnes wants to merge 1 commit into
t3/typescript-startup-stack-7-fetch-timeout-expansion-limitfrom
t3/typescript-startup-stack

Conversation

@kmcginnes

@kmcginnes kmcginnes commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Default Connection settings such as GRAPH_CONNECTION_URL were read only from -e flags and config.json. They now also come from .env and .env.local, in the same precedence order as every other setting.

Upgrade notes

  • Default Connection settings in .env and .env.local now take effect. The image's own .env sets SERVICE_TYPE=neptune-db and GRAPH_EXP_FETCH_REQUEST_TIMEOUT=240000, the same as the defaults. Remove connection settings from a mounted .env that you don't want used.

Evidence

After: the scenario rows with connection settings in .env and .env.local now expect them in the /defaultConnection body, behind -e and config.json.

Verified live: an image built from this PR on Colima passes every container step of the Docker workflow.

Merge Danger

Door: two-way

Impact: a mounted .env with leftover connection settings now changes the Default Connection.

Related


🤖 Written by an AI agent on my behalf.

@kmcginnes
kmcginnes added this pull request to stack #2613 November 13, 2026 23:39

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant