I want to install a URL shortener on a cloud VM for personal usage so that it will be very low volume. I have a few simple requirements:
- Runs in Docker
- As light resource usage as possible
- It must have authentication to prevent randos from using it
- It must be able to generate QR codes
- Modern and attractive experience ← subjective, I know
I have compiled the following options and pros and cons. Do you agree with this list and the pros and cons? Which do you think I should go with and why?
Kutt: Last release on Github: 2/22, 7,700 stars
Pros: Recommended here, fully featured, including authentication and QR codes
Cons: Heavy (3 containers), not recently updated
Yourls: Latest release on Github: 3/23, 9,700 stars
Pros: Recommended here, recent update, no native QR codes (but available via plugins), Lighter (2 containers)
Cons: PHP-based, less modern than Kutt, having to deal with plugins
Shlink: Latest release on Github: 9/23, 2,300 stars
Pros: Modern and attractive GUI, lighter (2 containers), bult-in QR codes, frequent updates
Cons: No authentication, Confusing and difficult install, separate front end and back end
Lynx: Latest release on Github: 8/23, 96 stars
Pros: Lighter (2 containers), native QR codes, authentication, frequent updates
Cons: Unclear experience – looks less modern on Github screenshot
RE: Kutt - see here: https://github.com/thedevs-network/kutt/issues/719#issuecomment-1788410446
I saw that the poster mentioned several PRs that the author should review. It seems that either the author has not or he thinks that they are less meaningful. Either way, it is surprising that there has been no new release for 18 months.
Microbin
I am a fan of Microbin and didn’t realize that it offered this. However, I am struggling with enabling authentication while keeping the ability to provide public pastas.
Shlink has API Key authentication. Why does a front end and backend make it a con?
Have been using Shlink for quite a while and it’s a nice project