tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-09-30 05:09:06 +02:00
Code Issues Projects Releases Wiki Activity

DOCS File migration background notes (#9058)

Browse Source
This commit is contained in:
Ingo Schommer 2019-06-21 08:47:40 +12:00 committed by GitHub
parent dcf4c64704
commit 0a6096a1bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/en/02_Developer_Guides/14_Files/05_File_Migration.md
View File

@ -42,7 +42,13 @@ When executing the task on CLI, you'll get colour coded error messages.
## Background migration through the Queuedjobs module
In general, it's safest to run the file migration on a non-production environment,
and switch over to the migrated assets and new database. That's not always feasible.
You can also run this task without CLI access through the [queuedjobs](https://github.com/symbiote/silverstripe-queuedjobs) module.
Due to the incremental nature of this migration, you need to consider how a partially migrated database
and asset store will impact your own site's behaviour, or how you can recover from migration errors.
When running a background migration in production, we recommend to put your site in maintenance mode to avoid inconsistent behaviour.
Open up `admin/queuedjobs`, then create a job of type `RunBuildTaskJob`.
The only constructor parameter allowed is the full name of the task: `SilverStripe\Dev\Tasks\MigrateFileTask`.
The task output will be progressively written to the job record, and can be inspected via the "Messages" tab within the job in the CMS.