From the sounds of it, it’s just a hobby project for fun for OP. I don’t think there’s anything wrong with doing something just for the sake of it.

I didn’t mean it as nitpicking. I was just responding to you?

I think FDE is different to full partition. If your home partition is encrypted but not your root partition, that’s not FDE. I would say FDE is when the partition that you mount to / is encrypted.

I don’t like JS either but it’s not a big deal. You can whitelist sites with noscript.

Automatic daily updates for system packages. Automatic daily container updates with watchtower. I normally have things pinned to a reasonable major or minor release, so I do manual upgrades for new OS release branches and usually pin to a major version for Docker containers but depends on the container.

For Q2: I would recommend your native layout. I’ve not tried US QWERTY but I tried DVORAK many moons ago because it’s “better”, but I found it’s better to be good at one layout than to try split your efforts. If you’re not doing something where speed is crucial, just use what you’re used to. If your keyboard layout is not good for your purposes (e.g. typing a character you need often for the programming language you’re using, is difficult on your layout), you could remap individual characters or maybe there’s a layout similar to your native one but better for programming. But no need to use US QWERTY specifically. Also as another commenter said, typing speed isn’t that crucial for programming. I find I’m always limited by thinking speed, not typing speed.

There was one question where it wouldn’t let me do this. I think the media streaming question I had to click “Other”.

Never used a dashboard… I just manage my services on the cli with plain docker commands.

Watchtower for automated updates. For containers that don’t have a latest tag to track, editing the version number manually and then docker compose pull && docker compose up -d is simple enough.

Yes, if you use the “task list” block. You can also have checkbox bullet points but I don’t use them, not really sure what the use-case for those are when you can just use the task list.

I self-host Notesnook and found it easy to set up. Been using it as my main note-taking app for years now and I’m really happy with it.

Someone who’s in the business of stealing computers would just stick it in a faraday bag. I guess for an entire server you’d need a sizeable cage though.

Idk about Immich but Vaultwarden is just a Cargo project no? Cargo statically links crates by default but I think can be configured to do dynamic linking too. The Rust ecosystem seems to favour static linking in general just by convention.

Yeah the intro read as weird to me. If you’re writing for a programming crowd there’s no need to explain all that, and anyway the rest of the article wasn’t about the stack/heap distinction.

I don’t think there is really any learning curve to “learning HTML” if you are not trying to do anything funky and you just want a simple static website that functions, like OP said, “like a business card”. You may as well just type it out yourself. If you’ve never written HTML before just look at w3schools.

I think once Forgejo gets ActivityPub integration working it will really help for migration. I know federated platforms like Mastodon struggled with adoption because I think a lot of folks struggled to wrap their heads around the fact that there’s no “default instance” and they have to choose their own instance, but hopefully for a programming crowd that won’t be an issue. It would massively help with the “well I could move to a different website but there’s no obvious second choice I can move to” issue; you can just head to any Forgejo instance and interact with any other federated instance.

You get a domain name, and use an A record to point it towards your server’s public IP address.

You tell nginx to forward requests to a given domain. For instance, you could tell nginx to forward requests to foo.bar.com to 127.0.0.1:1337. To do this:

http {
    server {
        server_name foo.bar.com;
        listen 80;
        
        location / {
            proxy_pass http://127.0.0.1:1337$request_uri;
        }
    }
}

Note that this is a very basic setup that doesn’t have HTTPS or anything. If you want an SSL certificate, look into Let’s Encrypt and Certbot.

Also, the service you’re hosting (which I’m not familiar with) may have an example reverse proxy config you should use as a starting point if it exists.

Been self hosting email for a good while now and it’s been largely painless. My emails are not getting marked spam either. Although my only outgoing mails are to FOSS mailing lists and occasionally to individuals, not for anything business related.

I would say that if self hosting email sounds like something you’d be interested in, then it probably is worthwhile for you. I like being able to configure my mail server exactly the way I want it, and I have some server side scripts I wrote for server side mail processing, which is useful as I have several different mail clients so it makes sense to do processing on the server rather than trying to configure it on my many clients. It definitely falls into the “poweruser” category of activities but I’ve had fun and I enjoy my digital sovereignty.

Do you have an old laptop somewhere? You shouldn’t need a new machine for a home lab if you’re just hosting services. Most of my self hosted services are on a fairly lightweight VPS.

And yeah, I’d second the commenter suggesting you look for a second hand computer somewhere instead of buying HP.

Simply make everything an array of bytes