4 ms·
Cool. This is quite usable and seems really handy—it's really fast compared to some heavier online repls. (definitely a use case for me) How is it set up? I wa
by 52-6F-62 7y ago
Cool. This is quite usable and seems really handy—it's really fast compared to some heavier online repls. (definitely a use case for me)
How is it set up? I was definitely able to crash an instance I was in as well as read from root, but seemed all it took was a reload of the page and it snapped right back in without any real startup wait.
*edit: I just saw that you posted the source code as well. I'll definitely be exploring!
- dijit 7y agoSeems like he spins up a container on each run, so 'root' is not really 'root'. I'd be worried though, containers are not secure enough to run untrusted code.
- maxmcd 7y agoyeah this setup seems to indicate it's just running regular docker: https://github.com/prasmussen/glot-run/blob/master/docker_server_config.md https://github.com/prasmussen/glot-run/blob/master/docker_se...
- mrmonkeyman 7y agoYour code breaks out of container to do what, exactly? I'm seriously curious what the worst case is here.
- pdexter 7y agoIt doesn't offer a repl as far as I've seen.
- 52-6F-62 7y agoYou're right. Fudged terminology. It does read-eval-print, but not in an interactive loop.