I suggest you ...

Clone from one server to another multiple times (change user on clone)

When you clone an app from one server to another, it keeps the same Unix/Linux user and MySQL database name, user and password. Thus, if you clone an app from one server to another, you can't repeat the process later, unless you delete the 1st clone.

We like to start with a base WP template app and another for WooCommerce. Then each time we start a new project we clone one of those templates to the server it's going to run on. Unfortunately after we do it from the server where the template resides to a new server, one time, we have to do it manually after that. It would be super helpful if cloning an app from one server to another would change the Linux user credentials, as well as the mySQL ones the same way that cloning an app from a server, to that same server currently does. Or at least provide an option to do this.

It saves a ton of time getting WordPress to a base configuration, if we can just clone our template each time.

11 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Tevya Washburn - FS shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
AdminCloudways (Admin, Cloudways) responded  · 

The logic behind keeping same creds is that many people use this feature to create test/dev environments, so it is convenient for them to have it like this.

In any case, for the flow you mention, you could clone a template from server A to server B. Then on server B, keep the first copy of the app as a template and clone it (on the same server) as many times as needed. Cloning on the same server changes all credentials, so this should work for you?.

Cloudways Team

5 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Scamando commented  ·   ·  Flag as inappropriate

    Yes, this would be awesome. It requires 2x cloning to make this work right now. First I have to clone to current server. Then I have to clone that new clone to other server. Then I have delete the first clone. Insane process. There should be an option that allows you to checkmark, "keep installation name, or create new name" when cloning to another server.

    https://getflywheel.com/why-flywheel/blueprints/ - This allows you to create multiple backups, Something like this would be ideal.

  • Tevya Washburn - FS commented  ·   ·  Flag as inappropriate

    It doesn't work for us, because then when we want to adjust our template site, we have to adjust it multiple times across multiple servers. We want 1 source app (2 actually 1-WP and 1-WC) that we can clone anywhere, but have it be able to be cloned to another server multiple times.

    I understand the logic, and we use it that way. But perhaps there could be 2 options: direct clone (current functionality) and "mimic" or something... I don't know the best word(s). Just an alternative that works the same way a clone does within the same server, but to another server. You don't have to change the functionality you have now, just add a checkbox or something to handle it differently for those of us that want to clone the same app multiple times from one server to another.

  • Tevya Washburn - FS commented  ·   ·  Flag as inappropriate

    That's a good idea. And we've thought of that. But it doesn't really work. The reason is that from time to time, we make changes and updates to the template, based on changes in plugins, themes, and settings as things evolve over time.

    If we did what you said, we'd have to either login to each of the template sites and make the same changes on all the templates (like 5-6 servers currently), which is a hassle. Or we'd have to delete them from all the servers, then re-clone from the "main" templates. Either is a hassle and not ideal.

    We understand the reason for keeping the credentials the same. And that's why we suggest just having a checkbox or something when doing the clone to allow them to be changed, or not, during that process. That way the clone can be done multiple times from server A to server B, if we, your clients/users want to, or not, if we want an exact duplicate for dev/test environments.

  • AdminCloudways (Admin, Cloudways) commented  ·   ·  Flag as inappropriate

    The logic behind keeping same creds is that many people use this feature to create test/dev environments, so it is convenient for them to have it like this.

    In any case, for the flow you mention, you could clone a template from server A to server B. Then on server B, keep the first copy of the app as a template and clone it (on the same server) as many times as needed. Cloning on the same server changes all credentials, so this should work for you?.

    Cloudways Team

Feedback and Knowledge Base