You are absolutely right. While there is the very fine reference documentation and the official wiki we just have no user-contributable “FAQ / Hardening / Best practice” documentation.
Well I don't really mean something like hardening since it's difficult to give generic advice for stuff which lies in the end in the responsibility of the administrator or software architect. To quote myself:
A hardening guide is actually not so easy since it depends on the threat model.
Just one example: NFS assumes that every Client can be trusted and ISCSI usually is not encrypted. While both might be acceptable in a strictly isolated corporate network, I wouldn't take this risk on a cluster of dedicated servers of some hosting provider or other zero trust environments.
So I doubt that there can be a "one size fits it all"-Tutorial.
In the end it's in the responsibility of the admin to create a thread and security model and configure everything accordingly.
https://forum.proxmox.com/threads/s...-hardening-wiki-page-be-created.148732/page-4
The reason I started this thread, that today I saw two or three threads on the same topic, how to backup pbs datastores with rclone to a cloud storage, which is something you really shouldn't do. I was kind of annoyed , because we had quite a lot of discussion on this not to long ago so I just inserted links to my posts in them. And this is not the only thing where it would be great if we could reduce to need the time to help people, who don't use the search function . Some other examples from
@LnxBil (mentioning him so he gets the credit) on page two of the linked thread above:
Yet, I feel your need for better documentation, but more for the volunteer people like us here, so that we can just reference stuff ... most of them not at all PVE related like:
- how memory is used in Linux and why my VM uses more ram than shown inside of the VM (at least once a week this is asked)
- best ZFS setup with or without L2ARC, additional metadata special devices and SLOG
- how to share files between VMs
- best backup strategy of files inside of my docker in my VM
- how to build "the best setup" with what I have ...
To be clear: I don't want to get the third person who ever got banned from Proxmox forums so dear staff and community member drop send me a pm if something rubs you the wrong way. I don't want to annoy or offend anybody.
The "natural" place would be the wiki under pve|pmg|pbs.proxmox.com, but probably that should really be left for Proxmox, the company.
I agree with this too
It would be weird to mix official information on licensing and legal stuff with community-sourced takes why helper scripts might be a good idea or not, why Linux using much RAM isn't actually a problem etc...
Actually I had thought about it some weeks ago. One specific aspect stopped my idea to mplement "something": maintaining an FAQ on the long run might be massively different from giving an answer here in the forum on the fly.
Sure on the other hand there are some precedents: To give credit where credit is due I got the idea after I saw an old talk from a German Opensource conference:
https://media.ccc.de/v/froscon2014_-_1489_-_de_-_hs5_-_201408231630_-_flames_-_kristian_kohntopp
The speaker remembered a time when the German Linux and PHP newsgroups (for the younger ones here: A kind of early forum, we oldtimers used beause we didn't had discord back in the days
) got a lot of posts from newbies who always asked the same questions without trying to look whether their might already somebody else asked that, even on the same day or week. Since the group culture of the linux newsgroups was at some point not in a good state but the PHP group was still quite new he tried an approach of "leading by example". He started a website/wiki with answers to often asked questions so if again the question would pop up he could drop a link to the corresponding article. This achieved two goals: First that people who took offense in lazy questioner could do something constructive on it without getting nasty. And second teach people asking for help, that they should look up whether there was already a solution for the problem. According to him for the PHP newsgroup this worked quite well (until Usenet died of course). He also remembered that the English C or C++ group (not sure it's some time I watched the talks video) did something simillliar, which not only resulted in a FAQ but also a book sourced from the entries.
After getting annoyed from the rclone questions I remembered the talk and thought it might be worth to try something simmiliar here.
Of course I could start in setting up an inofficial github pages repo for it but I would prefer to have some kind of official place for it and the forum seems like the best place to me.
So while it might be true, that it would be different and propably a certain investment at least I would prefer to spend my time in maintaining such a document instead of copy/pasting my earlier posting on the same subject. Your mileage may vary.