Ken
Good idea. But who has the access to all the hosting? If there is anybody who knows the hosting landscape, that is you! Still simply can look at all. So community has to contribute. Then, How? Above all, how do you motivate people to provide the data? People just want to consume, not produce.
I think the "things to avoid" is the easy part. More difficult, and sometimes controversial, are the preferred criteria. Do you really need 8 GB if don't have more than a dozen users? Or, what do you tell all those visit Hardware and performance asking for hosting specs for N-hundred thousand concurrent users?
More practical could just be a table:
- Shared/Root
- Linux distro
- Shell access (if shared)
- Git installed (if shared)
- Panel available
- Which panel(s)
- Cron service (if shared)
- RAM
- Disk
How about cache, Memcache, Memcached, Redis, Valkey,..
Doesn't have to be 250,000, even beyond 100 the site needs a structred search. See the Distrowatch search. Not an easy task. But then, I didn't check, there must be (too) many such compilations on the Web.
P.S. This is not exactly the "A super user friendly Moodle Installation website" in the OP. So renamed this sub-thread "A hosting chart".
P.P.S. I am still intrigued at what "A super user friendly" something is: Is it "A super, user-friendly" something or "A superuser-friendly" something?