Ah that makes sense. To be fair tho, there’s a lot of unwarranted hate towards Rust so it can be hard to tell.

I hope you’re joking. If anything, Rust makes error handling easier by returning them as values using the Result monad. As someone else pointed out, they literally used unwrap in their code, which basically means “panic if this ever returns error”. You don’t do this unless it’s impossible to handle the error inside the program, or if panicking is the behavior you want due to e.g. security reasons.

Even as an absolute amateur, whenever I post any Rust to the public, the first thing I do is get rid of unwrap as much as possible, unless I intentionally want the application to crash. Even then, I use expect instead of unwrap to have some logging. This is definitely the work of some underpaid intern.

Also, Python is sloooowwww.

I agree with the other comments saying that you don’t really need secure boot. But if you’re like me, you might be tempted to get it to work anyway. In that case, here’s a (hopefully) useful link.

I’m confused. What do you even mean?

It seems that I’d still need to modify net.ipv4.ip_unprivileged_port_start=80 in sysctl, which I don’t want to do. If I do it, the socket isn’t even strictly necessary.

Just a couple of friends use it. But I’d like to use this as a learning opportunity and do it the proper way. It seems that if I turn of masquerade in general, and use firewalld fine-grained rules to enable it when I actually need it, I might be able to achieve what I want. I’ll post an update to the original post if I can get it to work.

This is interesting. I need to figure out how it works for podman and it’ll be the perfect setup.

I think it’s the masquerade that’s causing problems for me. I have to keep it enabled since I’m running a tailscale exit node. But maybe I can selectively disable it here.

But that just makes most ports unprivileged. That is a solution, but less preferred than my current one.

I mentioned in the post that it seems to make the client IP opaque to caddy.

I had a very similar setup at one point, and what I did was just install Linux on the SSD. I’d recommend against mounting the HDD as /home as it’ll make your file manager feel sluggish, and would be an overall bad experience.

I used to just symlink directories from the HDD as ~/Pictures, ~/Music etc. and most software would just be able to work with those. You don’t really need to move software to your HDD since they rarely take much space, and moving to HDD will make them very slow.

For games, Steam and Lutris will let you select the installation directory on a per-item basis so you should be just fine.

That said, maybe you could use this opportunity to get a new larger SSD and then you won’t have to worry about this anymore. Also, you’ll be able to keep your important data on both drives, so you’ll have sort of a backup when something fails. (A more robust backup solution will be better, but hey it’s a start.)

All my servers run AlmaLinux. Install docker, openzfs etc. as needed. AlmaLinux offers a very solid starting point.

শুনে ভালো লাগলো যে এটা কারো চোখে পড়েছে। নয়তো সবাইকে বোঝাতে হয় কি নাম, কেন নাম। আসলে বাঙালী প্রোগ্রামার খুব বেশি চিনি না।

I’m happy that you like it. Any kind of analytics or logging is decidedly against my stated policy for this project, so I won’t be adding it. But I understand that some might need it, and in that case, one should look at more comprehensive solutions like YOURLS.

It’s just a way to advertise, I think. I’ve found myself putting more trust in projects written in Rust or Go, than say, JavaScript.

Hmm, so that might be out of scope here. But I can try to do some kind of 2FA, shouldn’t be much of an issue, really. It’s just that I never thought a link shortener needed 2FA protection since the links will be publicly shared anyway.

I don’t understand much about OIDC either. But I’ll keep it in mind. Thanks.

Unnecessary to me, I guess.

Thank you for the kind words.

Won’t lie, the main reason that I stuck to a vanilla frontend approach is because I didn’t know what else to do. I’ve never been a frontend dev, and never wish to be one. So I looked at an older project, and started by trying to replicate it. In hindsight, it was probably a good decision. The backend is more intentional though, and I do try to keep things simple and clean.

I’m already aware of a few small UI oddities. There were quite a few changes in the frontend, so I kind of expect these. Please let me know if you see anything weird. You can comment here, or open a bug report. I expect to do a patch release by tomorrow.