• 2 Posts
  • 169 Comments
Joined 7 months ago
cake
Cake day: August 25th, 2025

help-circle





  • I’m using windows 10 mostly, but I have another one made recently for win 11 because of another stupid manufacturer with stupid requirements.

    Once I made the first VM, I made a clone. The clone is what gets the software installation, the original just stays stored on my NAS so I can clone again as stupid manufacturers distribute stupid software that requires windows. I name each VM based on the app its going to run.

    Some are a suite of apps and companion applications, some are just a singular application.









  • Kind of the other way around there, starting with markdown to make a mindmap. Not that I haven’t used mermaid (though I’ll be candid, I mostly hate how mermaid renderers work and the layouts can get real funky real quick), but I’m more going the other way around. Start dropping stuff into a map, then sort it out after. For concepting things out, I like a GUI better. For documenting something existing, mermaid is a perfect decent option.






  • LXC is more focused on the OS than the application, where docker is more focused in the application. In general, I don’t recommend piping to bash, but take a look here for some lxc build scripts:

    https://community-scripts.github.io/ProxmoxVE/

    And you can still run docker with proxmox. You can make a VM and put docker in it, or you can run it in an LXC.

    Regarding VMs, that’s purely an example of how I am doing things, and only for specific things. I start and stop VMs because I’m passing specific hardware (a discrete GPU) to the VM, its not a shared resource in this case. I’m not making a virt GPU, the VM gets to use the quadro that’s in there directly. I have other VMs (HomeAssistantOS for example) that run all the time.

    LXC can be used to share resources with a host. VMs can be used to dedicate resources. LXCs are semi-isolated, and a VM is fully isolated.

    My example of the iGPU/dGPU is because of my use cases, nothing more.

    Clustering is easy and can be done over time. Your new host needs to join the existing server before adding any VMs or LXCs, that’s about it. A good overview of how to do it is here:

    https://www.wundertech.net/how-to-set-up-a-cluster-in-proxmox/


  • My setup doesnt matter, I don’t use Unifi for my main home infra.

    You can use the Unifi device itself. Teleport is just a single click Wireguard service, with no need for port forwarding or additional configuration.

    Last I saw it, you can export the config from the browser for use with client devices, you can use that with wireguard tunnel and set it as always on.


  • I am, though I’m not using unifi.

    Teleport is just Wireguard with unifi stacked on top. You can just export the config and its literally a Wireguard connection. Unifi Teleport is just using their online services to replace a step.

    But teleport (which is Wireguard under the hood) is not meant for an always-on connection, its meant for ad-hoc connections.

    So if you want always on, export the config and run it as a Wireguard tunnel. Its exactly the same service, running on exactly the same device, without using wifiman and allowing for an always on VPN.