# HG changeset patch
# User Link Mauve <linkmauve@linkmauve.fr>
# Date 1738099655 -3600
# Node ID f99f730f2b84c643b6208aa7d98eb54070e3b739
# Parent  983549664bd4e3bfff4a53595ae8a8fcc846bbf1
mod_storage_metronome_readonly: Add documentation about how to migrate a MUC domain

diff -r 983549664bd4 -r f99f730f2b84 mod_storage_metronome_readonly/README.markdown
--- a/mod_storage_metronome_readonly/README.markdown	Tue Jan 28 21:22:05 2025 +0100
+++ b/mod_storage_metronome_readonly/README.markdown	Tue Jan 28 22:27:35 2025 +0100
@@ -31,9 +31,10 @@
     storage = "metronome_readonly"
     data_path = "/var/lib/metronome"
 
-To run the actual migration, run this command:
+To run the actual migration, run these two commands (replace `<host>` with the domain you want to migrate):
 
-    ./prosodyctl mod_migrate <host> roster,vcard,private,cloud_notify,pep,pep_data-archive,offline-archive,archive-archive,uploads-archive sql
+    prosodyctl mod_migrate <host> roster,vcard,private,cloud_notify,pep,pep_data-archive,offline-archive,archive-archive,uploads-archive sql
+    prosodyctl mod_migrate muc.<host> config,persistent,vcard_muc,muc_log-archive sql
 
 It will create a file in `/var/lib/metronome/prosody.sqlite`, after which you
 can change your configuration file to point to it, or alternatively you can