Enhancement: Multiple endpoints
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Right now, we only can run chisel via one server endpoint.
However, sometimes we need to set up multiple ports that go to different end servers. In this case, we have to run multiple instances of Chisel, which gets very confusing and takes a lot of time to set up.
If we can do a config file with the ability to run multiple endpoint configs on a single instance of Chisel that would be very helpful.
Or even without a config file, perhaps add an option for multiple server sections i.e.
chisel client [options] -S [server] [remote] -S [server2] [remote2]
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
Start by tracing the chisel client command and how its options, server endpoints, and remotes are parsed. Define how multiple server/remote endpoint configurations should be represented and verify that one Chisel instance can run them without requiring separate processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100