oxidecomputer / oxidecomputer/console

VNC

Open
#2,354 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
228
Forks
22
Avg merge
19h 42m
Merged PRs (30d)
32

Description

We will soon have VNC. We will use NoVNC to VNC in the browser. We'll figure out the details when we try to make it work. NoVNC should at the very least be in a dynamic import to keep it out of the main bundle, like we do with recharts and xterm.js. It's conceivable but unlikely that we might even want a separate full JS bundle with its own index.html. (That would require changes to how Nexus serves the console, and for dubious benefit.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how the console currently loads recharts and xterm.js, then examine the planned NoVNC browser integration. Determine whether a dynamic import is sufficient or whether a separate JS bundle and index.html would require changes to how Nexus serves the console; done means the VNC approach is defined and integrated.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.