Selfhosted

I use this in my house, it's great. I chose this over others because it allows defining the url path specifically. (Domain.com/whatever)

I have all my pdf manuals and docs uploaded to Paperless ngx. From within Paperless I make them externally linkable.

I take those long nonsense links, shorten them using chhoto with meaningful paths (like /mitersaw) then convert all of those to qr codes that I print out and stick to whatever object is relevant.

Say if I'm working on my chainsaw or whatever and need the manual, point my phone at the qr code and open the manual from my network for my exact model.

It's neat that this exists, but not neat if someone hosts it for a year, a bunch of fed users rely on it and share a bunch of links using it, and then the hoster takes it down for whatever reason, and now there are a bunch of dead links littered all over the place.

Even less neat if some malicious group can then buy the lapsed domain and forward all those dead links to ads and viruses.

Please host responsibly, is all I'm saying.

Looks awesome and very efficient, does it also run with read_only: true (with a db volume provided, of course!)? Many containers just need a /tmp, but not always

So why would this need docker at all?

Please don't use url shorteners, this hides any information the url gives you about where it is taking you. Also most things on the internet support the concept of a link where the url is hidden behind friendly text but still inspectable without clicking by mousing over it.