A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Can I ask - why would anyone do this? Several URL shortening services of the past have shuttered and it has left the web littered with links to sites that can never be resolved (linkrot) - this to me just seems like a another surefire way to speedrun future deadlinks in forums etc. Why?
Edit - I have misunderstood the assignment.
This is targeted at self-hosted/personal-domain stuff only, not general internet site URL shortening/redirection.
I find link shorteners useful for sharing (ephemeral) links to others (especially if they're massive) but for linking stuff on the web where you can hide it under an anchor tag is definitely a bad idea.
How so? I am hosting and maintaining it for my own work and links. I have every incentive to keep it up. And if it goes down, only my links to my own content go down. And, the reason I did this was Bluesky has a character limit.
Ah that is probably my bad then, I read it as being able to redirect arbitrary URLs, hence the need for geoblock and abuse protections - if it's only your own self-hosted/personal domains then yeah that absolutely makes sense.
I think the concern re:geoblock is that the REST API is just out there, unauthenticated. I need to shut those off or limit them to the internal network with Traefik, but I still need the short links to resolve. I'm not sure if that API is used for that, or what. I haven't explored the code yet.
Another great option is Yourls. I’ve been using it for years and it’s been fabulous
I looked at yourls, too. I found Shlink devex to be more mature and the automated geolocation-blocking integration sold me.
It also hasn't had a release in 2 years and is a self-described "set of PHP scripts". Doesn't fit my standard for what I deploy to my homelab
Totally fair.
This maybe isn't for everyone but I de-dockerified Shlink pretty quickly. Moving it to two nginx vhosts (server and admin) on a Shlink LXC and a centralized Postgres server made dealing with it a lot easier.
E.g., the initial API key shenanigans were less fiddly after I took more direct control.
Interesting. I deploy to my homelab with Docker so it was a fit for me. But I do want to tinker on the API to disable everything but GET. Can you share anything more about breaking it up?
It was mostly uneventful, to be honest. I downloaded the two apps (static admin and the php app), tossed them into /opt/www, and set up nginx to serve PHP. The config in the main app had a section for my Postgres settings and the docs gave the instructions on putting the default server configuration into the static site.
The only challenge was actually rather silly: I don't use PHP so it took me a bit to understand why apt install php installed Apache when I had already installed nginx. Once I found php-fpm it was smooth sailing from there.