Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using ENV variables in Codegen #1450

Closed
wants to merge 1 commit into from
Closed

Using ENV variables in Codegen #1450

wants to merge 1 commit into from

Conversation

kerimhudson
Copy link

The intention behind this PR is to try and introduce the ability for the codegen to utilise environment variables rather than a databaseUrl string value to make it easier to commit to repositories and setup different environments where necessary.

This PR is still a WIP as there's some things that likely need to be considered about how these environment variables will work in various situations (such as within a Next.js project where they should be prefixed with NEXT_PUBLIC).

Closes #1440

Copy link

changeset-bot bot commented Apr 25, 2024

⚠️ No Changeset found

Latest commit: 6adce23

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@kerimhudson kerimhudson closed this by deleting the head repository May 25, 2024
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.

Set databaseURL as env variable in client file
1 participant