TRIM make clone (mirror) and make cloneandupdate or cloneandupgrade (pre-dogfood server)
- Status
- Pending
- Subject
- TRIM make clone (mirror) and make cloneandupdate or cloneandupgrade (pre-dogfood server)
- Category
- Feature request
- Feature
- TRIM
- Resolution status
- New
- Submitted by
- Marc Laporte
- Lastmod by
- Marc Laporte
- Rating
- Description
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-cloudb) 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-parityc) 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 copyThis 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:- https://sourceforge.net/p/tikiwiki/code/HEAD/tree/trunk/doc/devtools/update.dogfoodserver.sh
- https://tiki.org/Pre-Dogfood+Server
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+conflictsEspecially combined to the automated updates:
https://doc.tiki.org/TRIM#To_setup_automated_updatesPerhaps:
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..."
- Importance
- 3
- Easy to solve?
- 2
- Priority
- 6
- Demonstrate Bug on Tiki 19+
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Show.tiki.org is not configured properlyThe public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
- Demonstrate Bug (older Tiki versions)
-
This bug has been demonstrated on show.tikiwiki.org
Please demonstrate your bug on show.tikiwiki.org
Show.tiki.org is not configured properlyThe public/private keys configured to connect to show.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
- Ticket ID
- 5937
- Created
- Thursday 19 May, 2016 06:59:57 UTC
by Marc Laporte - LastModif
- Thursday 11 October, 2018 00:58:37 UTC