lae
lae
Closes #163 Possibly some stuff missing, actually. I have some changes for `prune-backups` stashed currently because I need to write more parsing logic around it so I'm putting that off...
So a lot of people have started using PVE for their VFIO setups, it looks like, and so have I recently. We can probably simplify the setup for it in...
Leaving this as a placeholder for myself, maybe I'll get around to it eventually. Last I checked Travis CI limitations aren't really favorable to me, so I'd like to move...
PVE 5.2 introduced ACME support within PVE. https://pve.proxmox.com/wiki/Certificate_Management An ACME management module can be created to manage ACME registration and certificate. Process I used to generate cert: ``` ~# pvesh...
By default `pam` and `pve` are realms created within Proxmox for authenticating users into Proxmox. This supports most use cases. However, Proxmox supports LDAP/AD realms, which some users may want:...
The Ceph configuration section in the README is a bit lackluster and requires the user to parse through the example provided themselves - of which some might not even be...
Source: https://github.com/znerol/prometheus-pve-exporter We should be able to: - create a new local unix user (`pve-exp`?) to deploy/run under, with random password (needs to be stored on the server somewhere so...
Should remain optional, but for single node installations this could be very useful. NAT network should be definable (in case user wants to route VMs on two separate NAT-style hosts...
We should be able to run a local instance of the Boulder CA and run tests against it: https://github.com/letsencrypt/boulder/ This should probably be done in the upstream systemli.letsencrypt role first,...
Hey guys. I haven't managed to proactively keep this role in sync with upstream (living circumstances over the past year and a half haven't been very conducive to many activities),...