HN Explorer

14 comments

[ 3.0 ms ] story [ 39.3 ms ] thread
johnhenry
This is really cool and useful. I hope you post this again and more people recognize it.
651549846546
Cool, Not seen the browser directory access permission before!

Is there any browser behaviour different than when using a file:// uri?

admax88qqq
I forgot the specifics but a fair amount of things no longer work from file URLs.

There's some much stricter rules on what your can access via fetch() if I recall.

slmjkdbtl
I think mainly CORS stuff, e.g. you can't use images loaded with file:// for WebGL texture, but also curious if more
nijave
I think there might be some script loading rules, too. That prevents JavaScript from an internet loaded site accessing local content
kevincox
It would be really nice if the files were served from the root. IDK exactly how that could be implemented. Maybe put the UI under an "unlikely" url. But then once you upload a lot of people will have a hard time finding the UI again to change the contents.
pie_py
$ python -m http.server

done.

nijave
PHP has a dev server, too
aussieguy1234
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`.

mft_
This looks very interesting - thanks for developing/posting.

Would it be feasible to allow different domains to be used - maybe for a fee?

videogreg93
Is this basically ngrok?
aussieguy1234
Yep, it's similar. I believe it can expose more than just web apps, for example SSH. I'm focusing my project on the web and making it easier to use.
aghilmort
super interesting -- are you exploring paid option + custom domain to make public?