All through the same network, I’m afraid. I haven’t felt the need to separate it like that, although it should be doable using docker networks, or maybe on even lower level, via Linux network namespaces.

Alright, so it can do some direct syncs via Garmin API, I didn’t know that. Last time I checked, only manually uploading your gpx files was possible.

Neat, I’ll definitely set this up. Dockerized, of course, my little server already has lot of services on it, got to keep things neatly separated. :)

So, what do you think of the Garmin intergration? I have had Fittrackee in my sights for a good while now, and the only thimg holding me back from trying it is that I donk know how painful (or painless) the activity upload/sync from my Garmin watch will be.

I just use my own custom built docker images and have a few aliases set up for different “instances”, e.g. one for banking, one for tis eshop, one for that eshop, etc. Each with its own firefox data dir and own downloads subfolder. Plus an alias to launch a temporary clean instance that gets discarded after it exits.

As a longtime Debian Stable user, I can attest that gaming on it works just fine, whether via Proton or natively.

It was rough at the first half year or so after Steam Linux client launched where system libraries were simply too old and one had to smuggle in libc from Ubuntu, but that got solved by the next Debian release, and it’s been smooth sailing ever since. :)

Of course, I wouldn’t recommend Debian for a gaming system for a newbie. It’s just what I’ve been using as my daily driver for decades, so I did not want to switch to something else just for something as unimportant as gaming.

Same here. I keep shaking my head in disbelief when I read all this “you need this custom niche distro if you want nvidia without problems” posts, and then look at my totally uncustomized Debian Stable PC, on which I’ve been playing modern games for many years now. :)

Really, the only trouble I’ve had was not Nvidia related at all - in the very beginning when Steam Linux client was released, Debian had too old glibc, and I had to resort to LD_LIBRARY_PATH/LD_PRELOAD tricks with glibc snatched from an Ubuntu package. But next Debian release fixed even that, and it’s been smooth sailing ever since.

Yep, Mastodon takes some effort to get going. You need to find people who are interesting for you yourself, in order to seed your feed with interesting stuff. And it goes much smoother if you also interact yourself, which is where many lurkers, used to Twitter and its algorithm feeding them content, hit a wall. It’s just a completely different world in there.