Sorry, that was presumptuous of me. ‘TCP stack’ just means each container can have its own IP and services. Each docker, and in fact each Linux host can have as many interfaces as you like.

I imagine you would get a conflict when you try to go to 192.168.1.2:8000 or even localhost:8000.

You’re free to run a service on port 8000 on one IP and still run the same port 8000 on another ip on the same subnet. However, two services can’t listen on the port at the same ip address.

mkvmake pulls the Forced flag from its source, so it’s likely that your DVDs have a set flag for certain subs. You can use mediainfo to check this on your mkv files.

Mkv is simply a container format, which means you can probably unset the forced flag with mkvmake directly without having to unpack all the streams and remux them.

Handbrake is amazing, but it does have a LOT of controls, so there’s only so much hand-holding it can do when you start looking behind the curtain of how av files work.

You will still have to make sure that port numbers don’t conflict

I’m sure I read you’re comment wrong, but you are aware that each docker container has its own tcp stack, right?

Thank you!

Thanks.

For severe incidents like this, please post the most appropriate link, in this case https://github.com/umami-software/umami/issues/3852

Admins in self hosted usually don’t have that much experience with real, active compromise and may panic, let’s help them as much as possible.

I will add that Umami itself is not compromised, but vulnerable. That is a somewhat misleading title.

What was the vector? Did you have umami exposed publicly?

Link? Did you discover this yourself? There is no actual info here.

Wow, armv7 is definitely back there in terms of support. One of the more known v7 devices was the nexus 7, released in 2012.

Makes sense. Your 2nd definition is what I take from the term scaling. Let’s see if op comes back with any notes.

For video encoding, I run an 8th gen Intel i5 8500t. The quicksync is good enough for nearly anything 1080p.

Not sure what you mean by the “scaling”.

Nice work. I would read more articles like these.

“Pleb” is generally used as a pejorative and is roughly equivalent to calling someone a peasant.

Are you not using LE certbot to handle renewals? I can’t even imagine doing this manually.

I don’t know… I’m skeptical of its bandwidth.

I love alpine, and I use it where I can. And it has many advantages over other distros and setups. But a declarative, ram-only distro that boots over the network doesn’t help manage non-conformant machines.

I still need to manage Debian, old centos boxes, Ubuntu machines, and a couple old-as-time sun machines. Nixos isn’t the tool for that job. Ansible has two dependencies: ssh and python, and there are ways around the 2nd one. Ansible works really well here.

Not trying to bash nixos, here, but I’m not sure why so many users on Lemmy compare ansible and nix, they don’t really operate in the same spaces.

Can you manage a Debian server with nix?

Hahaha nice. I have PTSD from teaching the interns how to search graylog and then locking up elastic with piped conditional searches.

I appreciate the response.

I’m still keeping an eye on these technologies and I hope we can set some decent standards for alternates to WiFi and LTE narrow band.

I’ve been watching halow for a while, I haven’t yet seen any sustainable, real-world examples beyond a few hundred kbps (not bytes). I have seen the 1Mbps results, and they’re promising, but most places with any other traffic in the free band is busy. If you have any successful and repeatable tests hitting at usable speeds, I’d love to see them.

After getting into meshtastic and a few other lorawan projects, I’m a bit concerned that tests for these are always high and visible, which doesn’t work well in the mountains, even at shorter ranges.

I used to be more hands-on with these new standards, but I’ll wait for better tests to come from halow before I try it out.

Definitely possible, and there is already some tech with the kinks worked out like wimax that could wirelessly serve a whole town. There are also folks who have created their own isps to fill in where the big players don’t bother. It is apparently regulatory hell to get up and running.

The problem isn’t technology, it’s people.

Like every protocol in the unlicensed 900mhz range, 802.11ah has a very limited transmission rate in the 50 to 100 kbps range.good for occasional data like sensors or a few bytes of message, but not for any modern comma like AV, mass file transfer, etc.