Give Developers More Control Over Cache and Security Settings
Cloudways is convenient for managing servers, but some routine tasks still feel unnecessarily restrictive for developers running production websites. Cache management and security configuration are two areas where having more granular controls would make a noticeable difference.
Instead of forcing users to purge an entire cache whenever a single PHP file, page, or asset changes, Cloudways could provide an option to purge cache for a specific URL or file. This would be especially useful for custom applications where developers may need to test frequent changes without affecting cached content across the entire website.
The same principle should apply to common ModSecurity settings. Parameters such as SecRequestBodyNoFilesLimit and SecRequestBodyLimit are useful when applications handle larger requests or uploads, yet changing them currently requires contacting support. Adding these settings to the Cloudways control panel would give developers more control over their own server environment.
These changes would not require Cloudways to become overly complicated. A simple Purge by URL/File option and a small ModSecurity settings section with clear limits and warnings would be enough. More granular controls would make Cloudways easier to work with when developing, testing, and maintaining real-world applications.
horror games
anna alexsmith123
shared this idea