feat(stripe): add env vars for STRIPE_PUBLIC_KEY #62
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…kerfile and CI workflow
beniaminmunteanu
requested review from
golobitch,
raducristianpopa,
dragosp1011 and
Tymmmy
Tymmmy
previously approved these changes
May 15, 2025
…f remix env variables, revert dockerfile and workflow
Tymmmy
approved these changes
May 15, 2025
dragosp1011
approved these changes
May 15, 2025
beniaminmunteanu
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR intends to make the build&publish workflow create and publish 2 separate interledger-pay images.
This is done in order to have 2 separate images for interleger-pay to be used in test and cards(prod) environments.
Needed in this particular case in order to use separate stripe publishable keys on these separate environments