marionebl/share-cli

🌍 Quickly share files from your command line

Quickly share files from your command line

Demo created with svg-term-cli: cat demo.json | svg-term -o demo.svg

share-cli

• 🚀 Dead simple
• ✨ Just works
• 🔒 Encrypted files

share-cli exposes files via HTTP, either from stdin or a given file glob.

The exposing address is copied to your clipboard automatically. Files are made available as password-protected, encrypted ZIP file.

Installation

npm install -g share-cli

Usage

❯ share --help

  Quickly share files from your command line

  Usage
    $ share [file]

  Options
    --no-tunnel  - Disable localtunnel usage

---

share-cli is built by Mario Nebl and released under the MIT license.

share-cli's Issues

Separate CLI from logic

So it can be used programatically 😄 for CI situations or similar

[Question] How to be possible share a browser?

Hello,

I love how minimal and focused is this project. Thanks for that!

In order to extend the idea, I want to the same but for bcat.

bcat is just a simple tool to pipe any UNIX command to them and print the output in a browser instead of the terminal

The point is, this tab runs on my local – Could be possible convert the that into a shareable thing? then anyone with the link can see the output, it would be very useful for debugging things.

How I can replicate share functionality to use the same logic but for a different purpose?

🙂

dependency missing - xclip on ubuntu

http://stackoverflow.com/questions/27688804/how-do-i-debug-error-spawn-enoent-on-node-js/27688805#27688805

spawn called
{ '0': 'xclip', '1': [ '-selection', 'clipboard' ] }
/home/developer/.nvm/versions/node/v4.3.2/lib/node_modules/share-cli/cli.js:328
throw error;
^

Error: spawn xclip ENOENT
at exports._errnoException (util.js:870:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:437:9)
at process._tickCallback (node.js:351:17)

I solved this by sudo apt-get install xclip, you may want to update the docs

Does not load the "Opening tunnel"

$ share udemy.pdf

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move data fetching code or side effects to componentDidUpdate.
• If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
• Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Provider
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Prepared file
✔ Server started
⠧ Opening tunnel
Copy
✔ Downloads: 2

Closing in 60s
Ctrl+C to close now
Ctrl+R to allow more downloads
^C

Does not load the "Opening tunnel"
I use MacOS system

error spawn zip ENOENT

any idea about this error?

$ uname -a
Linux cdm6_58 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ sudo apt install npm
$ sudo npm install -g share-cli

$ share myfile.txt
✖ Preparing file failed
  Server
  Tunnel
  Copy
  Download

spawn zip ENOENT

sharable directories

Make directories shareable by automatically zipping the directory. currently this action throws an error:

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: EISDIR: illegal operation on a directory, read
    at Error (native)

Making zipping possible, the current directory could be shareable by typing share .

After successfull sharing or timeout the archive should be deleted.

This module uses 117% CPU

Not sure why it does this, but its incredibly slow for me

To reproduce:

1. Go to repo readme where image is at
2. Launch chrome task manager

Getting 404 error after entering IP address

I am getting 404 error after putting IP address in the endpoint in provided url, please help.