Yeah, it can for sure. Definitely worth mentioning. Gotta watch what interface is set as the default router, or you’re bound to have a bad time. That said, the same is true with his originally proposed solution of pushing a trunk port to the VM, so it’s not any worse in that regard.

But yeah, full agreement on the correct solution. Keep it simple.

I wouldn’t let every VM have an interface into your management network, regardless of how you implement this. Your management network should be segregated with the ability to route to all the other VLANs with an appropriate firewall setup that only allows “related/established” connections back into it.

As for your services, having them on separate VLANs is fine, but it seems like you would benefit from having a reverse proxy to forward things to the appropriate VLAN, to reduce your management overhead.

But in general, having multiple interfaces per VM is fine. There shouldn’t be any performance hit or anything. But remember that if you have a compromised VM, it’ll be on any networks you give it an interface in, so minimizing that is key for security purposes. Ideally it would live in a VLAN that only has Internet access and/or direct access to your reverse proxy.

Ah, gotcha. Thanks! :)

Maybe it’s cause I’m on mobile, but I just see the intro paragraph, unless I’m missing something on how to see a full article?

Do you really think the reason people hate Java is because it uses an intermediate bytecode? There’s plenty of reasons to hate Java, but that’s not one of them.

.NET languages use intermediate bytecode and everyone’s fine with it.

Any complaints about Java being an intermediate language are due to the fact that the JVM is a poorly implemented dumpster fire. It’s had more major vulnerabilities than effing Adobe Flash, and runs like molasses while chewing up more memory than effing Chrome. It’s not what they did, it’s that they did it badly.

And WASM will absolutely never replace normal JS in the browser. It’s a completely different use case. It’s awesome and has a great niche, but it’s not really intended for normal web page management use cases.

I’d rule out k8s if you’re looking for simple administration.

Not to state the obvious one, but there’s always the Raspberry Pi.

The supply has gotten better on those, so you can probably pick one up in your price range, and the power draw is super minimal.

Fair.

In addition to the other suggestions then, you could always just use VLC and the VLC Remote app that lets you control it from your phone.

Seems the easiest solution. No extra services to set up or anything. Literally just a video player with an app to control it from your phone.

I think there’s some confusion here over your proposed set up.

What device do you imagine having plugged into the HDMI of your TV? Is it your laptop or something else?

Are you intending on watching the videos through the web front end you’re imagining, or just using the web front end as a “remote control” as it were?

I don’t think most of the responders have a clear vision of what you’re going for.

https://www.dagusa.com/