fix: remove ream devnet flag #78
Open
+0
−7
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Recently ream removed support for the runtime-based flag (ReamLabs/ream#1099). This PR removes the deprecated devnet flags that were causing launch failures in both docker and binary modes.
Important Note
Since the devnet selection is now a compile-time feature, you must ensure that your ream binary is built with the appropriate feature flag enabled if you are using the binary setup mode.
For example, to build for devnet1 (default):
For devnet2:
NOTE: If you are using the docker image, ensure the image is built with the desired feature enabled.