Live data from Hacker News

Servefolder.dev

servefolder.dev

1–10 of 15 posts

Re: Servefolder.dev

#4

Cool, Not seen the browser directory access permission before! Is there any browser behaviour different than when using a file:// uri?

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.

Re: Servefolder.dev

#5

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

Re: Servefolder.dev

#6
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.

Re: Servefolder.dev

#9

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?

Post reply on HN