Dear Cloudways team,
I’d like to suggest a potential improvement to your staging environment system, specifically regarding WordPress installations that include subfolder setups.
Currently, the push/pull functionality works well for the main WordPress installation. However, when a subfolder WordPress installation exists within the primary site directory (e.g., /public_html/subsite/), the staging feature doesn’t distinguish between the main and subfolder installations. This means the staging site can only perform push/pull operations for the main WordPress instance, not for a separate subfolder WordPress installation.
Proposed Improvement
It would be very useful to:
Allow the staging environment to recognize and handle subfolder WordPress installations separately from the main installation.
Enable users to create and manage staging environments independently for both the main and subfolder WordPress installations.
Provide distinct push/pull options for each environment (main vs. subfolder), ensuring that data and files are correctly synchronized between production and staging for the selected installation only.
Use Case
Many developers run multiple WordPress instances under the same hosting account — for example, a main site and a subsite (e.g., /blog, /app, /portal). Having independent staging control would:
Prevent accidental overwrites of the main site.
Simplify testing and deployment of changes for subfolder installs.
Offer better flexibility for multi-site or hybrid setups without needing full multisite configuration.
I believe this feature would significantly improve the staging workflow for developers who manage complex WordPress setups.
Thank you for considering this suggestion. I’d be happy to provide more details or examples if needed.
Kind regards,
Milos Bogdanovic