I suggest you ...

WordPress (or other apps) staging (live and test site combination)

Cloudways definition of staging is somewhat different from other managed WP services like SiteGround and MT Premium WP. It would be great to have dual WP setup for live and test without cloning, and hopefully with easy/simple sync feature.

176 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    mottainaisan shared this idea  ·   ·  Admin →

    34 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • AdminCloudways (Admin, Cloudways) commented  · 

        @devcode

        Yes, it will perform the search and replace for domain that is being mapped as primary domain in Cloudways Platform..

        For instance on production app, you have primary domain mapped as www.example.com, and in both the case case i.e Push (from Live to Staging) or Pull (to Staging from Live) primary domain will be replaced by the Cloudways provided Staging domain.

        Hope this answer to your question.

        You can also refer to the KB as follows https://support.cloudways.com/create-staging-environment-site/
        where we have listed all the details related to the feature.

        Cloudways Team

      • devcode commented  · 

        Does the push and pull works with the domain interface? Swapping and rewriting all urls from example.com to staging.example.com and vice versa? In all files, typically:
        Database
        wp-config.php
        .htaccess
        etc?

        Not using Cloudways that's why I'm asking :)

      • Erin commented  · 

        Hey guys, loving the new staging feature and have used it quite a few times now so super happy with it! Everything seems to be working well, except a recent issue I've discovered in pushing changes from staging to live. The edit and adding of plugins is replicated but the removal of plugins isn't. So for example, I removed a few plugins in staging that were still there after pushing to live. Although the plugins I added or edited in staging came across to live as expected. I have proven this on two seperate applications.

      • Anonymous commented  · 

        need this feature! please check this out.

      • Anonymous commented  · 

        It would be great to get an update on the progress of this much needed feature. Thanks!

      • Austin commented  · 

        I too would like to know where Cloudways stands on this feature request. It's a much-needed function!

      • Sanjeev S commented  · 

        We are past mid June and wondering if there is any update on this as this was supposed to roll out last month. Please advise. Thanks,

      • Maxime commented  · 

        Any update on this?

      • Anonymous commented  · 

        I can't migrate my clients to Cloudways until there is a functional workflow similar to:
        prod -> dev (clone)
        prod -> stage (clone)
        dev -> stage (merge)
        stage -> prod (merge)

      • Anonymous commented  · 

        Staging please. I am sure that the increase in number of clients would more than make up for the development of a proper staging option.

      • Josh commented  · 

        Any updates on staging? This is a must-have for multisites.

      • Matt commented  · 

        I’ve read a couple articles but all of your competitors have a much simpler process.

        This is the one missing element that has been keeping me from immediately moving my clients to Cloudways.

        1. Allow for creating a snapshot of the production site as the staging site.
        2. Allow setting my custom domain with a staging URL, such as a subdomain
        3. Allow for publishing (overwriting) the production site with my changes.
        4. Allow for taking a new snapshot of the production site to overwrite the staging site again.
        5. Do NOT overwrite any traffic data when publishing changes from staging to production.
        6. Make sure all URLs when publishing from staging to production use the Production format...not the staging URL.

        Again, WP Engine, Flywheel, and many others have done so beautifully. But, I do not enjoy paying PER WordPress site...especially when a client has two tiny WordPress sites.

      • Chris commented  · 

        A true staging environment for WordPress sites is a must. Please look at implementing this feature ASAP.

      • Anonymous commented  · 

        I agree with all the comments here. The Cloudways solution is not "more flexible," it's just less functional. What's missing is a tool to push database changes. At minimum, there should be a set of syncing options.

      • pee commented  · 

        I see that this is one suggestion with the most votes, where cloudways does not have acted upon yet! Please consider adding this! :)

      • pee commented  · 

        I am evaluating cloudways for over a month, and i mentioned this several times to support: cloudways promises staging environments on its pages but does not deliver it I read the comments of the staff, but they make no sense. STAGING IS NOT CLONING! We really need an automatic deploy from staging to production WITH DATABASE SYNC AND USING GIT in an automated way for wordpress (and others)
        please listen to your customers and add this soon. Many other providers have this already, and this is my no 1 reason, not to move all my sites to cloudways.

      • Ryan commented  · 

        The ability to push from a staging to production is one a the key reasons I haven't moved all of my WP site from WPEngine to Cloudways yet. The ability to pick files and/or database changes (and exclude tables) is a key part of our development workflow.

      ← Previous 1

      Feedback and Knowledge Base