11–15 of 15 posts
Cool, Not seen the browser directory access permission before! Is there any browser behaviour different than when using a file:// uri?
I think mainly CORS stuff, e.g. you can't use images loaded with file:// for WebGL texture, but also curious if more
$ python -m http.server done.
If you have node, "serve" does pretty much the same thing. `npm install -g serve` then `serve .` If you want a public URL you could try my side project, `expose` ( https://expose.sh ) in conjunction with `serve`.
This looks very interesting - thanks for developing/posting. Would it be feasible to allow different domains to be used - maybe for a fee?
If you have node, "serve" does pretty much the same thing. `npm install -g serve` then `serve .` If you want a public URL you could try my side project, `expose` ( https://expose.sh ) in conjunction with `serve`.
Is this basically ngrok?