How about a QR-code in the terminal? about miniserve HOT 11 CLOSED

Yeah, I think that'd be cool and helpful.

from miniserve.

That's a cool idea. How would we decide on which IP the QR-code would target ? An argument like --qr-code=my.public.ip.address maybe ?

from miniserve.

Maybe we can figure out the local domain (from /etc/resolv.conf domain) and hostname and construct the full local hostname that way?

from miniserve.

I think we could borrow a lot from Quair. Specifically local IP address detection and how to display a QR code in the terminal. EDIT: we can't actually copy-paste code because it's MPL2 and miniserve is MIT. But we can see what libraries they use, and things like that. Also maybe the quair developer would like to join forces with us, since they seem to have similar goals.

qrcodegen looks like a great option for generating the SVG version of the code for use in the web interface.

from miniserve.

Yeah, quair seems really neat. I wish it were a library. The IP stuff seems easy enough.

from miniserve.

There also is https://github.com/kennytm/qrcode-rust which does image, svg and text encoding of QR-codes.

from miniserve.

We now have a QR code in the HTML. We don't yet have one on the terminal but I'd be open for that option, too.

from miniserve.

@svenstaro

If the user uses the -i option, the content of the QR code should be http://{-i}:{-p}.

If the user does not use the -i option, then search for interfaces, then the content of the QR code should be http://{interface}:{-p}.

Looks like this:

miniserve v0.7.0
Serving path .../miniserve at http://[::]:8080, 
http://127.0.0.1:8080
██████████████      ██  ██████████  ██████████████
██          ██  ██  ██  ██  ██      ██          ██
██  ██████  ██        ██  ██████    ██  ██████  ██
██  ██████  ██  ██        ██  ██    ██  ██████  ██
██  ██████  ██  ██  ██████      ██  ██  ██████  ██
██          ██  ████████      ████  ██          ██
██████████████  ██  ██  ██  ██  ██  ██████████████
                  ██  ██  ████
  ██  ████  ██████████        ██  ██  ██████  ██
██    ██  ██      ████          ██    ████  ██████
██  ████    ██    ██  ██      ██    ██████  ██  ██
██  ██    ██  ██  ██  ██████            ██      ██
██        ████  ██  ████    ████  ██      ██    ██
██████  ████    ██      ████    ██  ██      ██████
████████  ████████████████    ██  ██    ████    ██
████  ████      ████████  ████  ████    ██      ██
      ██    ██    ██    ██  ██████████████  ██  ██
                ████    ██  ██  ██      ██    ████
██████████████  ██  ██  ██      ██  ██  ████  ████
██          ██            ██    ██      ████  ██
██  ██████  ██  ████      ██  ████████████  ████
██  ██████  ██  ████████    ██      ██  ████    ██
██  ██████  ██    ██  ██    ██████          ████
██          ██  ████  ██  ████  ████      ██████
██████████████      ██████  ████    ██████████████
Quit by pressing CTRL-C

It should be noted that how to print the QR code when using multiple -i? Or print multiple QR codes?

from miniserve.

Hm yeah, I wonder. I think multiple QR codes would be weird. Maybe only print the IPv4 QR code to be safe?

from miniserve.

If only one QR code is printed, then when we run:
miniserve . -i 127.0.0.1 -i 192.168.0.40
What should be the content of the QR code?

from miniserve.

Haha, good point! Well, maybe it does make a good deal of sense to print one QR code per listening interface, then.

from miniserve.