Problem: Currently, a Let's Encrypt SSL is tied to a single CloudWays App, so there are delays in dropping and re-applying for an SSL when bringing an App into production on another domain.

CW Tech Support could not suggest a smoother way to bring an App into production, which makes CW a bad option for active sites. I'm inclined to run my own server where I can atomically move a symlink to go live or various other ways of smoothly transitioning from dev to production.

Solution: SSLs should be tied to their corresponding Domains, not a single App. This would:

• allow for quickly swapping domains between Apps and having the SSL follow the corresponding domain.

• incorporates the suggestion to allow a wildcard SSL to be used across multiple Apps:

https://cloudways.uservoice.com/forums/203824-service-improvement/suggestions/45104782-allow-wildcard-ssl-certificate-to-be-used-across-m