LXC is much more light weight than VMs, so it’s not as much overhead. I’ve done it this way in case I need to reboot a container (or something goes wrong with an update) without disrupting the other services

Also keeps it consistent since I have some services that don’t run in docker. One service per LXC

I run a different LXC on Proxmox for every service, so it’s a bunch. Probably a better way to do it since most of those just run a docker container inside them.

Second impression of Garuda (Arch based). My first impression was the dragonized version, which is KDE with lots of mods to make it Mac like, but with extra window animations.

I like things simple, so when I tried Garuda again, I installed the Gnome version. Other than some weirdness getting my Nvidia card working with Wayland, it has run better than anything else on my laptop.

Fully agree with this. There will be a slight learning curve since it will be different from what your used to, but it’s friendly enough to figure out.

If you know the windows program you want to use just search something like “Linux alternative for x” (sometimes there is specific KDE or Gnome progs)

SOLUTION:

Here is the solution I came up with:

pub struct Configuration {}

impl Configuration {
    fn get std::str::FromStr>() -> Result {
        Ok(T::from_str("1234");
    }
}

fn main() {
    let my_conf_val = Configuration::get();
}

Afraid this might have been the case, if Ogeon’s suggestion doesn’t work out, I’ll probably end up with multiple getters, one per type. There aren’t that many anyway

Thank you!

Correct, I would want the caller to know what they’re getting, I’ll see if this works, Thank you!