Servefolder.dev
servefolder.dev
Servefolder.dev
1–10 of 15 posts
Re: Servefolder.dev
#2Re: Servefolder.dev
#3Is there any browser behaviour different than when using a file:// uri?
Re: Servefolder.dev
#4Cool, Not seen the browser directory access permission before! Is there any browser behaviour different than when using a file:// uri?
There's some much stricter rules on what your can access via fetch() if I recall.
Re: Servefolder.dev
#5Cool, Not seen the browser directory access permission before! Is there any browser behaviour different than when using a file:// uri?
Re: Servefolder.dev
#6Re: Servefolder.dev
#7done.
Re: Servefolder.dev
#8If you want a public URL you could try my side project, `expose` (https://expose.sh) in conjunction with `serve`.
Re: Servefolder.dev
#9If 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`.
Would it be feasible to allow different domains to be used - maybe for a fee?
Re: Servefolder.dev
#10If 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`.