You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submitted by JamieCameron on Fri, 12/16/2016 - 00:45 Comment #6
The main reason that a domain owner cannot clone their top-level domain is that the clone would also be a new top-level domain. Presumably what you'd like is for the clone to become a new sub-server that the user could make changes to for testing purposes?
Perfectly put! Let the top-level domain be clonable as a sub-server of its own. Our purpose was not make them clone another top-level domain, but to make sense of the available features and options. Users should be able to clone their domains into development, testing, stage and various versions of their websites, main (top-level) or sub doesn't matter.
Submitted by JamieCameron on Fri, 11/02/2018 - 01:06 Comment #10
I must have forgotten about this request - it seems do-able, although presumably you'd just want to clone the web content and databases and not mailboxes?
The text was updated successfully, but these errors were encountered:
Summary quotes from https://www.virtualmin.com/node/44836 which perfectly explain the subject matter:
The text was updated successfully, but these errors were encountered: