Resolve #63, improve .env imports on deploy scripts #64
Conversation
This file contains 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
dubzn
approved these changes
Jan 9, 2024
JuArce
reviewed
Jan 10, 2024
JuArce
approved these changes
Jan 12, 2024
rcatalan98
approved these changes
Jan 12, 2024
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 way of importing .env variables to a bash script is better because it has greater readability, it does not need to change its implementation across different OS , and it resolves variables from .env such as:
STARKNET_KEYSTORE=~/.starkli-wallets/keystore.json
to
/home/user/.starkli-wallets/keystore.json
This avoids deployment bugs, for example when users paste the keystore location with " ~/ ", which is greately used across our different tutorials