On 7/30/21 3:43 PM, Abhilash Raj wrote:
Hi folks. Some time ago, I set up mm3 and have been running a bunchof 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 inretrospect, I installed mm3 from my OS' package repository.
Yeah, I know, that was dumb. Now I'd like to migrate to a newserver, and I'd like to install mm3 in the normal way.
Is there a way that I can "dump" the configuration from an existingmailman3 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
migratecommand to upgrade the database. The exact migrate command depends on how you install the new one (mailman-web or django-admin --settings settings).
Ok. I guess first I've got to figure out where the database lives. I've not been hacking on mm3, just using it.
I'd also say you should avoid updating database versions in this process because that would just add another variable to the process.
Sounds reasonable.
Thank you, I appreciate the advice.
-Dave-- Dave McGuire, AK4HZ New Kensington, PA