3 ms·
I'm a new dev at Linode, and this is the first product I helped ship. It was very fun to work on - we used Node to write all of the glue that gets noVNC to talk
by Sir_Cmpwn 11y ago
I'm a new dev at Linode, and this is the first product I helped ship. It was very fun to work on - we used Node to write all of the glue that gets noVNC to talk to qemu behind the scenes. LMK if you have questions, I can probably answer them.
- zxcvcxz 11y agoIs any of the work open source? I'm also a node/js dev and this sounds like a project I would be interested in.
- Sir_Cmpwn 11y agoI sent some fixes up to noVNC (along with the colleagues that worked on Glish with me), but our node work is closed source and will remain so since it deals with some internal things like authentication. However, we have some pretty cool open source projects in the pipeline for the coming weeks/months/years/decades.
- Rapzid 11y agoPretty cool. I did a similar integration back in 2011 for a VPS provider when we shipped Windows. I ended up writing an auth provider for noVNC proxy though that verified a token passed in against a new endpoint in our API(with a bunch of security checks and expiry of course). Worked pretty well after cleaning up the proxy a bit(particularly the logging). I'm guessing Linode needs to handle a bit more load than we did of course :)