-
Notifications
You must be signed in to change notification settings - Fork 59
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
docs: locally connect documentation #335
Conversation
## [0.45.2](v0.45.1...v0.45.2) (2024-04-24) ### Bug Fixes * added breakpoints to debug ([1f754b6](1f754b6))
## [0.45.3](v0.45.2...v0.45.3) (2024-04-25) ### Bug Fixes * apple pay debugging ([#333](#333)) ([ca96770](ca96770))
## [0.45.4](v0.45.3...v0.45.4) (2024-04-25) ### Bug Fixes * apple pay debug ([34d4828](34d4828))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removing environment variable based configuration completely and just relying on the .env
file would be a backwards incompatible change.
can use the .env file to complement the environment variables instead.
if we wanna just rely on file based config using a separate .yaml / .json/ .toml file would be a better norm... (instead of .env files)
…-connect-documentation
…erswitch-web into locally-connect-documentation
…-connect-documentation
Type of Change
Description
Added .env file for connecting locally for our backend services and client url changes.
How did you test it?
Run the backend locally and add the required keys for the same to test setuo works as expected or not.
Checklist
npm run re:build