Braun and Dakota are the most questionable of these releases.

Well, unless you feel like writing that feature into this project, perhaps you could modify your requirements slightly. Copying your local file to a share that’s also mounted to this handbrake-web instance would accomplish the same goal - taking local files and having them processed by this backend service.

https://github.com/TheNickOfTime/handbrake-web

While this post is in support of a self-hosting platform, the request itself is storage-related. I would recommend that you reach out to https://lemmy.world/c/zfs or https://discourse.practicalzfs.com/.

Right. You kind of want your bare metal OS as vanilla as possible. If you need to nuke and pave, you don’t need to worry about re-applying various configs. Additionally, on a theoretical level, if there’s a bug in something on the bare metal OS, the separation provided by VMs and containers should mean it doesn’t affect the the apps in those VMs / containers.

That seems easier - at least to me - than keeping track of configs in text files or even Ansible playbooks.

Have you considered searching the GitHub issues?

Curious how this is distinct from SimpleX.

Leaving this post here since it’s an interesting project to keep an eye on, but the conversation isn’t constructive. So, locking the comments.

Would they have to be VLAN aware if the switch port was already tagged AND if OP doesn’t care to consider untagged traffic ?

With the disclaimer that Proxmox has nothing to do with this question, I’m forced to assume this is just a networking issue that happens to use OPNsense as the router. Because of that, I must advise that you seek help from a networking-focused community. There’s no clear link to self-hosting in this post, which is required per Rule 3.

If the connections are already tagged as you come into the Proxmox server, then you need only to create interfaces for them in Proxmox (vmbr1, vmbr2, etc). EDIT: if you’re doing PCI passthrough of the physical NICs, ignore this step.

Then, in OPNsense, you just adding the individual interfaces. No need to assign a VLAN inside OPnsense because the traffic is already tagged on the network (per your earlier statement).

Whether or not the managed switch that has tagged each port is also providing VLAN isolation, you’ll simply use the OPNsense firewall to provide isolation, which it does by default. You’ll use it to allow the connections access to the fiber WAN gateway.

You’ll need to be far more descriptive than “I can’t get it to work.” I can almost guarantee you that Fedora is not the problem.

https://perfectmediaserver.com/

I’m a little lost on how a container would mess with your boot loader (GRUB). That aside, most of what you’re explaining to do with the containers. These are OS-agnostic. What do the container logs tell you?

This is really more of a home networking issue than anything having to do with self-hosting, especially since it centers on a consumer router. Please consider posting this in one of the many Lemmy home networking communities.

I’m going to allow this post, despite its age and likely obsolescence. I encourage community members to use up and down votes to judge its value to the community.

I am with you on the advantages of running it in a VM. The isolation a VM provides is really nice. Snapshots FTW.

TL;DR: No sleep = tired = low energy = eating for energy = overeating

I feel this, too. I’m averaging 4-5 hours/night. I know that I eat at night to get energy to stay awake and carry on.

That’s not a definitive support statement about Docker being unsupported. In fact, even in the Admin Guide, it only provides recommendations. The comment I replied said Docker is unsupported by Proxmox. I maintain that there is no such statement from Proxmox.

Proxmox is Debian at its core, which is supported by Docker. There’s no good reason to not run Docker on the bare metal in a homelab. I’d be curious to know what statement Proxmox has made about supporting Docker. I’ve found nothing.