This repository was archived by the owner on Jun 14, 2018. It is now read-only.
Exposing TRUFFLE_NETWORK in the node process #34
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Hello there,
I'm proposing a quick work around, so we can work around the current lack of flexibility with the environment / deployment issue. The idea behind this patch is to expose the selected network as an environment variable, so that the process can introspect itself and be aware of the current environment.
This is a practice coming from the rails community. The command:
$ rails c production
will seed RAILS_ENV with production.
Thank you for the amazing work!
Best,
Ludovic