I've updated webcode so that owners of endpoints can configure "public livecoding", which allows any logged in user to grab the public traffic to that endpoint (well, each logged in user gets their own fingerprinted endpoint, so traffix is not mixed between users). So finally I can write a public demo of livecoding. This article is maybe too long but its how to implement a webserver including: serving and responding to web forms, serving a dynamic image (e.g. dashboard), and streamed responses. webcode offers a fairly low level HTTP interface so achieving most of those things requires a fair amount of HTTP knowledge, hence I thought I would just write it up. https://observablehq.com/@endpointservices/livecode

[Moved from top level. Original post by @Peter Saxton] This is cool. Certainly, the first time i've seen anyone else make the client a server. I made a proof of concept of a similar thing a while back. https://spotless.run/ Though I had no idea of making it a business, and the notebook angle is cool.

Thanks @Peter Saxton. spotless is very interesting. How did you do the custom domain per function thing? I really need to do that too. I've had the idea for dynamic functions in my head for many years (since working on Firebase Functions and hearing every customer complain about deploy times), but it wasn't until I met Observable that there was enough external infrastructure around to make doing it worthwhile. You need a good editor for code content that is URL addressable... though these days there are other options like vscode.dev so I am wondering if I should branch out and make it a library.

Hey. I just use a wildcard domain and then make the domain part of the routing logic here https://github.com/midas-framework/spotless/blob/master/proxy/lib/spotless/router.ex#L53

Which wildcard hosting provider do you get? Or you running you own vm with letsencrypt

I don't think I have SSL