And I just made an HTTP endpoint in golang that outputs PNG labels with small QRs just as I need them, to print out on my Bluetooth label printer.
And I just made an HTTP endpoint in golang that outputs PNG labels with small QRs just as I need them, to print out on my Bluetooth label printer.
Please elaborate,
The software looks ok, will install. UI looks like spoolman, no bs, just works. I like it.
But; what’s with the label printer? Creating qr with a url to the inventory system looks handy.
I always have to dig thru gmail for order confirmations when I want to know where stuff was bought. This looks like a great solution for a first world problem.
I keep track of lots of vintage devices in my basement, these lay on a CD shelf with narrow walls, and I want to keep track of their maintenance status, i.e. when did I charge the battery last time.
This little printer is pretty handy for labeling tasks, with one noticeable problem: the resolution is quite low, so I cannot afford printing full length domain name on such a tiny label. What I ended up with is writing my own microservice that puts fake http://i.nv/ domain in front of inventory ID. That domain is provided by DNSMASQ that I run on my server, and there’s also NGINX listening for that domain and doing 302 onto an actual Homebox page.
Homebox sends URL parameters to the specified endpoint, and given that information it is possible to construct any label of any shape or form, it only needs to be a PNG image.
Thanks for the answer!
Just bought a phomemo, looks like smart folks created a cups driver for it. (Ab)using dnsmasq and nginx is clever, will keep that in mind.
Perhaps not relevant in your case, but if you print qr, the caps of your links also affect the amount of data in the code:
https://hackaday.com/2025/02/26/shout-for-smaller-qr-codes/
Surprisingly, it works! I just checked it on my microservice, indeed now QRs are smaller. This is a lifesaver tip, thanks a bunch!