On Fri, Jul 30, 2021, at 12:06 PM, Dave McGuire wrote:
Hi folks. Some time ago, I set up mm3 and have been running a bunch of lists on it with great success. I was a long-time mm2 user, and while the differences are significant, I'm glad I made the switch.
However, in what seems to have been a moment of insanity in retrospect, I installed mm3 from my OS' package repository.
Yeah, I know, that was dumb. Now I'd like to migrate to a new server, and I'd like to install mm3 in the normal way.
Is there a way that I can "dump" the configuration from an existing mailman3 server, and "import" it into a new instance? I'd really like to avoid re-doing all of the configuration, etc, as there are quite a few lists and everything is set up pretty much the way I want it.
You can copy the database from your old install to the new install
using the database native tools (or just point the new install to the
same old database if that is a possibility). Mailman Core will upgrade the
database schema when it first starts to the latest version's expected
schema. For web-components, you'd have to manually run the django's
migrate command to upgrade the database. The exact migrate
command depends on how you install the new one (mailman-web or
django-admin --settings settings).
I'd also say you should avoid updating database versions in this process because that would just add another variable to the process.
I would appreciate any advice from this learned group.
Thanks, -Dave-- Dave McGuire, AK4HZ New Kensington, PA
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)