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)
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tikiwiki.org instance. To start, simply select a version and click on "Create show2.tikiwiki.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.tikiwiki.org.
The URL for the show2.tikiwiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tikiwiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|