Show HN: Add live runnable code to your dev docs
37 by mlejva | 12 comments on Hacker News.
Hi HN community, I'm Vasek, co-founder, and CEO of Devbook [0]. Devbook is an SDK that you add to your docs website and then every time a user visits your dev docs, we spin up a VM just for that user. The VM is ready in about 18-20 seconds. We haven't had enough time to work on optimization but from our early tests, we are fairly confident we can get this to about 1-2 seconds. In the VM you can run almost anything. Install packages, edit & save files, run binaries, services, etc. You as a documentation owner have full control over the VM. We give you full access to filesystem, shell, stdout, and stderr. You don't have to worry about any infrastructure management. It's just one line of code on your frontend. On the backend, the VM is a Firecracker microVM [1] with our custom simple orchestrator/scheduler built on top that just gets the job done. We chose Firecracker for 4 reasons: * (1) the security with a combination of their jailer * (2) its snapshotting capabilities * (3) quick booting times * (4) option to oversubscribe the underlying server resources This allows you to create a whole new set of interactions between your dev docs and a developer visiting the docs. We've had users building coding playgrounds [2] to show how their SDK works or adding embedded terminals to a landing page [3] to show how their CLI works. The way Devbook works is that you use our frontend SDK [4] on our website. The SDK pings our backend and we boot up a VM. The VMs are ephemeral and get destroyed after a while of not getting pinged. You can predefine what the VM filesystem will look like through our CLI via a simple Dockerfile [5]. We also have an open sourced UI library for components like terminal, file system explorer, or code editor [6]. The need for Devbook came from our own frustration with dev docs. It has always felt strange that dev docs contain so much code but none of it is actually runnable. You as a developer have to set up full environments to see how the API works and get a deeper understanding. We are very early so we don't offer self-serve for now. A bit of manual work is still required when we are onboarding new customers. We are looking for some specific use-case that would make our go-to-market strategy much easier. It feels like the product we offer is way too general. We basically say "here's a whole computer, have fun". I'd love to know what you think about it. I'll hang out here and I'm happy to answer your questions! [0] https://usedevbook.com/ [1] https://ift.tt/Gx6v8zA [2] https://ift.tt/N86wB3d [3] https://runops.io/ [4] https://ift.tt/MNrv32t [5] https://ift.tt/xOQ0E7N [6] https://ift.tt/3lEQAIk
37 by mlejva | 12 comments on Hacker News.
Hi HN community, I'm Vasek, co-founder, and CEO of Devbook [0]. Devbook is an SDK that you add to your docs website and then every time a user visits your dev docs, we spin up a VM just for that user. The VM is ready in about 18-20 seconds. We haven't had enough time to work on optimization but from our early tests, we are fairly confident we can get this to about 1-2 seconds. In the VM you can run almost anything. Install packages, edit & save files, run binaries, services, etc. You as a documentation owner have full control over the VM. We give you full access to filesystem, shell, stdout, and stderr. You don't have to worry about any infrastructure management. It's just one line of code on your frontend. On the backend, the VM is a Firecracker microVM [1] with our custom simple orchestrator/scheduler built on top that just gets the job done. We chose Firecracker for 4 reasons: * (1) the security with a combination of their jailer * (2) its snapshotting capabilities * (3) quick booting times * (4) option to oversubscribe the underlying server resources This allows you to create a whole new set of interactions between your dev docs and a developer visiting the docs. We've had users building coding playgrounds [2] to show how their SDK works or adding embedded terminals to a landing page [3] to show how their CLI works. The way Devbook works is that you use our frontend SDK [4] on our website. The SDK pings our backend and we boot up a VM. The VMs are ephemeral and get destroyed after a while of not getting pinged. You can predefine what the VM filesystem will look like through our CLI via a simple Dockerfile [5]. We also have an open sourced UI library for components like terminal, file system explorer, or code editor [6]. The need for Devbook came from our own frustration with dev docs. It has always felt strange that dev docs contain so much code but none of it is actually runnable. You as a developer have to set up full environments to see how the API works and get a deeper understanding. We are very early so we don't offer self-serve for now. A bit of manual work is still required when we are onboarding new customers. We are looking for some specific use-case that would make our go-to-market strategy much easier. It feels like the product we offer is way too general. We basically say "here's a whole computer, have fun". I'd love to know what you think about it. I'll hang out here and I'm happy to answer your questions! [0] https://usedevbook.com/ [1] https://ift.tt/Gx6v8zA [2] https://ift.tt/N86wB3d [3] https://runops.io/ [4] https://ift.tt/MNrv32t [5] https://ift.tt/xOQ0E7N [6] https://ift.tt/3lEQAIk
Comments
Post a Comment