From fad2059021b08d8a31e2b109afe20b26f913af74 Mon Sep 17 00:00:00 2001 From: Amigo <49749100+aamigo@users.noreply.github.com> Date: Tue, 30 Jul 2019 12:17:56 +0200 Subject: [PATCH] Updated 039 Automated backup system in JCB (markdown) --- 039-Automated-backup-system-in-JCB.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/039-Automated-backup-system-in-JCB.md b/039-Automated-backup-system-in-JCB.md index 28d2b76..429b9fa 100644 --- a/039-Automated-backup-system-in-JCB.md +++ b/039-Automated-backup-system-in-JCB.md @@ -10,7 +10,7 @@ This is a demonstration of the new automated backup feature that has been added [00:01:07](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m07s) -JCB already has in its component area an export component feature, which we extended to automate. We've left it as a button called backup. It is the same feature except you can manually trigger that feature. Now what backup feature does, either being triggered by a [00:01:36](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m36s) CronJob or being triggered by backup button. It takes all your components and exports them, encrypts them, stores them on a local folder, and emails the key to a trusted email address which you have set up. [00:01:58](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m58s) The components that are in your trash will not be part of this backup. Only components that are published or unpublished or archived, will be in the backup, everything else will be ignored. Basically when the backup runs either manually or automated via a CronJob, [00:02:26](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m26s) it will take those components, use the specific keys as it would with an exporting of a components. Encrypt and store them in that folder as I said. +JCB already has in its component area an export component feature, which we extended to automate. It has been left as a button called 'Backup'. It is the same feature except it can manually be triggered. It can either be triggered by a 'CronJob' or being triggered by Backup button.[00:01:36](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m36s) What the backup feature does, it takes all your components and export them, encrypt them and store them on a local folder, and then emails the key to a trusted email address which you have set up. [00:01:58](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m58s) The components that are in trash will not be part of this Backup. Only components that are published or unpublished or archived, will be in the Backup, everything else will be ignored. Basically when the Backup runs either manually or automated via a 'CronJob', [00:02:26](https://www.youtube.com/watch?v=GUWZaODo_IM&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m26s) it will take those components, use the specific keys as it would with an exporting of a components. Encrypt and store them in that folder. <<<<< ### New Features - Mail Configuration, DKIM, Encryption Settings, CronJob Tabs Added