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.

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.

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.

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.

Why ZFS?

I think in general people start out in VMs and advance to containers. If you are already using containers stick with it, otherwise you are taking a step back.

Interesting perspective—I had thought that running an entire VM would be more difficult, but I’ve never used virtualisation for server stuff, only ever used VMs with a GUI VM manager on my personal computer. Thanks for the input.

I think you should open a Forgejo issue requesting a cache size limit option. It seems like quite a big problem if bots can fill up your hard drive like this without you setting a limit on all data used by Forgejo (when, for single-user instances, you probably only want to limit archive size or size of any data the public can create, not the size of your own repos)

Codeberg Pages. Neocities.

You’ve not made it clear what exactly it is you want. Nextcloud or syncthing are good for syncing personal files. If you want to make server backups, they’re not gonna be the way.

If you want to automate backups, you could just use a cronjob to make a tarball and rsync it?

I see, that’s interesting. Well glad that it’s not hard to switch away from systemd on Debian for those who want it—although I still think if you don’t want systemd you should just pick another distro, given that the Debian installer doesn’t let you pick another init.

On Debian you can use both sysvinit and openrc

Huh really? Then why does Devuan exist? (I don’t use Debian for context)

I use Alpine for servers because I like its simplicity. Not in terms of computational power requirements, just in terms of user experience.

Alpine is an interesting choice for hosting

I’d say servers are one of the main uses of Alpine, second to containers. It would be a much more unusual choice for a desktop OS.