Support a list of servers that are cycled on reconnect
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 168
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
This would lead to bundling the hostname, port, tls settings so that each entry in the list could have a different setting.
servers:
* name: "example"
remotes:
* hostname: "this.chat.net"
port: 6667
* hostname: "that.chat.net"
port: 7000
tls: yes
I'm not sold on what remotes should actually be, however. Perhaps servers becomes networks and then remotes could be servers
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes a YAML-like configuration for multiple remotes with per-entry hostname, port, and TLS settings, but names and structure remain undecided. Start by resolving whether the concepts should be called servers, networks, or remotes, then locate the configuration entry point. Done means reconnecting cycles through the configured endpoints while preserving each endpoint's settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100