Is there a mod repository ? How to make mods ?

[Johannes S]

What you mainly seem to be looking for is automated means to create standard, often-used VMs on Proxmox.

And even for that I think that using docker-compose or ansible-playbooks would be a better way then some hellish scripts.

(although they are not point-and-click. For that, use Unraid).

In general if one just wants to set up some services for a home network a NAS os with docker support (doesn't really matter which) is imho more novice-friendly and less-maintenance effort than ProxmoxVE. YMMV

 

[meyergru]

Correct, but basically, the scripts are on Github, open for scrutinization. Ansible playbooks can hold the same amount of hellishness as any script.
Considering IDK of any inherent Proxmox "qm" support in Ansible, I suspect that you would have to resort to shell calls anyway in such playbooks.

I do not say anything about the quality of those scripts, but they may be the way to go for someone who does not want to follow the all-available instructions to set up any of the standard tools as VMs, LXCs or docker containers. All you need to have available is a standard Linux (probably Debian) template as a basis.

You are correct in pointing out that whoever does not want or cannot follow such instructions should not be using Proxmox anyway and use Unraid or a NAS box that already comes with an "app store" for these purposes. Proxmox is not the right tool for those people.

 

[shodan]

"whoever does not want or cannot follow such instructions should not be using Proxmox"

"Proxmox is not the right tool for those people."

Well fine then stay difficult

 

[meyergru]

It is not me "staying difficult". I am not responsible for Proxmox development - I only realize that there are two kinds of tools for almost any purpose:

a. user-friendly, easy to manage tools. Those are often quite limited in what you can achieve with them - otherwise they needed to be more complex to offer a larger degree of freedom.
b. expert tools. Those are often more complex to configure, yet they offer much more flexibility.

As examples, tools in category a are Unraid or for firewalls, Fritzboxen.
Tools in category b are Proxmox VE and for firewalls, pfSense or OpnSense.

You can't have the cake and eat it, although you obviously do not like that answer. Or you theoretically could, but the effort needed to make a tool of type b user-friendly takes more development effort than is commercially viable. And people who actually pay for these expert products (i.e. buy the business license) do not need this kind of end-user flexibility.

 

[VictorSTS]

Well fine then stay difficult

Mate, it's super simple: use the API to interact with PVE and make your tool to do whatever you need. A script, a GUI, a docker, a full blown app... and let everyone to be happy. There are lots of examples with this approach.

IMHO: no one wants PVE to become "the wordpress of hypervisors", specially given how fragile and unsafe any app that allows code mods is. Just the idea of it gives me chills!

 

[shodan]

I don't understand, you prefer to run random scripts from github repositories and have no way to remove them, revert them, changing their application orders ?

I find that doing these modifications is hugely time consuming, irreversible, break things and then you have to wipe the disk clean and start over from nothing.

I understand that keeping thing difficult increases job security for operators and prevents their users from doing useful things without having to ask their admin for stuff.

I just think not having a system to at least add and remove mods in a standard way shows a rigid stubbornness that is anything but useful.

With all the time I have to open the console (and it's often breaking copy paste functions), I might as well just do everything with the qemu cli directly.

At some point fiddling around in the homelab, twiddling thumbs waiting for the proxmox installer to re-wipe the disk

has to make way for the actual getting of things dones, some people have things to do beside reinstall proxmox for the 3rd time

 

[VictorSTS]

you prefer to run random scripts from github repositories

Personally, I never ever run any script from anywhere. Not even from known sources like ttek / community scripts[1]. Never really had the need for it, neither in my homelabs nor in any of the clusters I manage.

and have no way to remove them, revert them, changing their application orders ?

No idea what are you referring to. You apply them in which ever order you want and you are responsible of knowing what they do, what they modify, etc. If you run a script that modifies core PVE files, it's your responsibility and you would be doing something that from a maintainability and safety should not be done.

I understand that keeping thing difficult increases job security for operators and prevents their users from doing useful things without having to ask their admin for stuff.

Absolutely nothing prevents you to implement whatever functionality you want in your app and use the API to interact with PVE. Some examples in no particular order here [2]

I just think not having a system to at least add and remove mods in a standard way shows a rigid stubbornness that is anything but useful.

If even after this you still feel like that, let's just agree that we disagree. IMHO you should try to change your point of view and adapt to PVE instead of trying to adapt PVE to yourself.

[1] https://github.com/tteck/Proxmox and https://github.com/community-scripts/ProxmoxVE
[2] https://github.com/gyptazy/ProxLB https://github.com/ansible-collections/community.proxmox https://www.modulesgarden.com/products/whmcs/proxmox-ve-vps-and-cloud https://corsinvest.it/cv4pve-cv4-tools-proxmox-suite-open-source/

 

[meyergru]

If even after this you still feel like that, let's just agree that we disagree. IMHO you should try to change your point of view and adapt to PVE instead of trying to adapt PVE to yourself.

Well, you can do that, iff that is within your range of capabilities - I just would not expect anybody else to do it for you.