[Feature Request] Remote Terminals over Websocket
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Sorry if my request doesn't make any sense, as I do not fully understand the architecture of hyper.
However, if I am correct to assume that Hyper is essentially a web application with a FE and a BE running on the local machine i.e. an electron application, then it should technically be possible to move that BE to a remote machine e.g. a server in the cloud and then wire the FE and BE using e.g. websocket e.g. as used in codesandbox?
Note this is different from using SSH in that all the connections will be over HTTP (for handshake, then TCP) and will not require any firewall/network configuration.
If so, how complicated would that be? e.g. complications that might arise due to limited network bandwidth for streaming buffers, etc.
Thanks!
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
No files or tests are named. Start by mapping Hyper's frontend/backend Electron architecture, then assess how a remote backend and WebSocket connection would affect terminal buffer streaming, bandwidth, and network behavior; done would be a decided implementation scope rather than an open feasibility question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- backend, desktop, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100