Introducing Multiple Default Peers per User #230
Closed
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.
I've introduced two new configuration options:
default_peers_per_user
anddefault_peer_names
. Now, when a user is created, the program will automatically generate a number of peers specified bydefault_peers_per_user
. Shoulddefault_peers_per_user
exceed the number of names provided indefault_peer_names
, the program will revert to the existing naming convention for any additional peers.Should this enhancement be approved, I plan to update the documentation accordingly within this pull request.
To maintain compatibility with existing setups, I've set
default_peers_per_user
to default to 1. Furthermore, I've retained thecreate_default_peer
option for now, although it could potentially be phased out. In the future, simply settingdefault_peers_per_user
to 0 could serve as the indicator for whether or not peers should be created.