Carries operator-edited email templates out of the database and into files.
Message templates are moving from phoenix_kit_email_templates to files a
host owns in its own repository, where they are version-controlled and
reviewable. This task is the upgrade path: it writes every row an operator
actually edited into the layout core reads, so those edits survive the table
being retired.
mix phoenix_kit_emails.templates.exportRun it, review the diff, commit the files. Nothing is deleted and no database row is touched — the database layer still wins at send time until the table is dropped in a later release, so an export that turns out wrong costs nothing but the files.
What gets exported
Only system templates an operator actually edited. Untouched ones are skipped (core supplies those itself now, translated into every shipped locale), and operator-authored rows are left alone — those are newsletter layouts, and they keep a table and an editor.
PhoenixKit.Modules.Emails.TemplateExport decides all of this and documents
why, including the locale rule that governs the filenames.
Options
--dry-run— report what would be written, write nothing.--force— overwrite existing files. Refused by default, so a hand-written override is never clobbered by a re-run.--out DIR— target directory (defaultpriv/phoenix_kit_templates).