|
|
|
|
|
by adlwalrus
5004 days ago
|
|
Seems like this could be done with more respect for user/data sovereignty if done with Node.js. Essentially, you'd cat the file into the script, it would spin up an HTTP server, do some port knocking or whatever NAT-traversal-fu is necessary, then spit out a link with either your raw IP, or a preconfigured dynDNS domain name. This way we aren't carelessly littering our data all over the "cloud". |
|
$ pagekite.py /path/to/file.blah yourname.pagekite.me
... send people a link to https://yourname.pagekite.me/file.blah and it streams from your disk. CTRL+C and it's offline with no copies stored anywhere in the cloud. Works with entire folders too (append +indexes to generate indexes), which is good for static HTML demos. If you want a harder-to-guess URL, append the +hide flag to the command above.
And yes, it's open source and you can run your own relay/reverse-proxy if you don't want to rely on me. Give it a try! :-)