Instead of having users search the internet endlessly for stupid php limitation problems. Why not offer a CPANEL and SERVER with UNLIMITED RESOURCES. As most executives are tech dumb, you can offer unlimited storage and databases without actually being able to use either. The solution... unlimited php resource hosting. Never have to touch the caps because its all maxed out already. You want to upload to your wordpress. Done. Doesn't matter what it is. Doesn't matter at all. Just works. Period -> .
I can only think back to the first real problem i had. Max_Execution time. Max_Upload . This is where everyone's career begins because it is problem #1. Spend days of my life unneccesarily. If GoDaddy already would've PRESET it TO MAX, then it would've saved my hands about 10k clicks of the mouse.
Hi @sparxx. Thanks for the suggestion. Before I can pass on your feedback, I need to understand it a little better. When you say unlimited resources, do you mean specifically things like max_execution_time and max_file_uploads or are you referring to resources like RAM, I/O, etc.?
For the former, most server admins put PHP limits in place to help protect the overall environment of the server. This is especially important in shared hosting environments where the resources for the server are split up between multiple customers. PHP limits help safeguard against programs that are misconfigured using all the resources available for the account. However, they are often configurable to allow more flexibility.
For the latter, server resources are usually limited in some way based on the physical memory that's available on the server (RAM, HDD space, etc.). If a customer wants access to all of the resources available on a server, we do offer dedicated server hosting.
The only type of server that I can think of that wouldn't have physical limits would be something that grew as demand increased. We did have a cloud server service for a while a few years ago that allowed developers to create their own servers and only pay for what they used (similar to services provided at AWS) and expand them as needed. However, that turned out to not be a good fit for us and most of our customers, so it was discontinued.
The server setup right now stinks. The object of technology is creating an environment for your health. Which in our industry is clicking a mouse or least amount of mouse clicks. You are absolutely incorrect. Those limitations were put in place because in the original programming nobody in their right mind would've believed that anyone would need more. Now 10 years later, we need more. All that stuff should be preset to the ceiling. Almost nobody would even use it. But I would. Having to click and troubleshoot and remember has wasted tons of clicking with my hands. What a waste if there was just someone who could ensure that the server will always be in a pre-programmed state of Ferrari. The absolute max capability for php pre-programmed for my pleasure enjoyment time and the saving of my fingers clicking a mouse.