See: Tiki DB Redactor
Although it would be nice, this doesn't need to be automatic on a cron job like A backup script that can be put on a cron job to save to a distant backup server
Amette explained that he copies data to a new database and that he executes various operations on this database.
So in essence, a cloning command is necessary for this. And a clone and upgrade is needed for show.tiki.org
If clone and redact was available on the command line, as a cron job, it could be an extra parameter to a clone command. See: Command-line tool
And when we'd become quite confident with our script, we could even make the backups available to the public, like Wikipedia does. This is one more reason why fully automated would be nice.
1st use of this new process is to supply redacted copies of tiki.org, doc.tiki.org and dev.tiki.org to Matthieu Hermet to work on NLP with ElasticSearch.
There are plans to automate this, but the current procedure is:
Run setup.sh and when prompted for the multitiki instance, put "redact". This will create the local.php in db/redact/local.php
Modify the db/redact/local.php to point to the database you want to redact (it is recommended that you make a copy of your database first).
php console.php --site="redact" database:redact
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.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.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.tiki.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.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.
The URL for the show2.tiki.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.tiki.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|