Allow a "default" grid/connection to be specified via config.txt #292
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
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 adds support for optionally specifying a "default" grid/connection via
config.txtas follows:The presence of this option at runtime replaces the "Invite Code" field/widget on the welcome widow with a "Connect to " button which, when clicked, creates a
tahoenode using the settings provided by the cheat code specified (thus, in the example above, a "Connect to Demo Grid" button will appear which, when clicked, will load the grid-configuration settings found atgridsync/resources/providers/demo-grid.json).This (completely optional) setting is intended to be used for custom deployments of Gridsync -- for example, in the event of a user-testing session in which the "invite code" step might need to be skipped, or for commercial deployments that may want to ship "pre-configured" builds to users.