Servefolder.dev

servefolder.dev

47 points·AshleysBrain··14 comments

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?

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.

This looks very interesting - thanks for developing/posting.

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

Yep that is an option, you can subscribe at https://dashboard.expose.sh, set your api key (copy and paste what's shown) then run `expose` like `expose 80 as mysite.expose.sh`

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.

$ python -m http.server

done.

PHP has a dev server, too

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.

I think mainly CORS stuff, e.g. you can't use images loaded with file:// for WebGL texture, but also curious if more

I think there might be some script loading rules, too. That prevents JavaScript from an internet loaded site accessing local content

This is really cool and useful. I hope you post this again and more people recognize it.

super interesting -- are you exploring paid option + custom domain to make public?

Reply on news.ycombinator.com