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
https://www.stickermule.com/marketplace/3442-there-is-no-cloud
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.
http://12factor.net/dev-prod-parity
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)
Perhaps:
make clone : a one-time copy
make mirror: setup automated recurring copy
This script should have access to system configuration and to run a profile. An example is $site_closed eq 'y' and $site_closed_msg="This is a copy of XYZ..."
Use case 2- pre-dogfood (test upgrade)
Like:
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:
https://dev.tiki.org/Check+if+the+update+would+cause+conflicts
Especially combined to the automated updates:
https://doc.tiki.org/TRIM#To_setup_automated_updates
Perhaps:
make cloneandupdate (test minor update)
make cloneandupgrade (test minor upgrade)
This script should have access to system configuration and to run a profile. An example is $site_closed eq 'y' and $site_closed_msg="This is a copy of XYZ..."
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |