Use case 1- mirror a site
Be able to provide on same server (different URL) or different server a fresh identical copy of Tiki with all data, including files that are not in DB.
a) Could be to offer a backup site on a different server in case main server is down. This backup site could be in the customer's office, so avoid any cloud lock-in: "You have a fully working instance with all data (less than x hours old) and all the FLOSS code on a computer you physically control" And this sticker can go on the box
b) Could be part of a dev/staging/prod routine. Ex. push data from prod to staging and/or dev to 'reset' and now we start developing again.
c) Could conceivably be used to have several copies of a site and load balance via DNS but there would likely be better ways to achieve this... (ex. MariaDB Galera Cluster)
d) demos (OpenSourceCMS type demo to test/develop and show off profiles)
make clone : a one-time copy
make mirror: setup automated recurring copy
Use case 2- pre-dogfood (test upgrade)
That script works but it's a manual configuration every time. TRIM can backup, deploy and upgrade so why not combine?
a) Check at any time how an upgrade would impact.
Could be to the tip of same branch or to the tip of a future branch or trunk.
b) Could be part of a dev/staging/prod routine
And adding a conflict alert with this would be really nifty:
Especially combined to the automated updates:
make cloneandupdate (test minor update)
make cloneandupgrade (test minor upgrade)
|No attachments for this item|