On 07/25/2018 06:55 AM, Ryan McClung wrote: > The mailman 3.0 install is on the same box as 3.2. Is there a quick and > dirty way to flip over?
Other than updating your MTA and web server to point at the 3.2 install, you need to ensure that 3.2 accesses the old 3.0 database(s) and after doing so, run the django management 'migrate' command. The core's migrations should be done automatically by alembic. Note questions like this will reach a deeper pool of knowledgeable people if asked on the [email protected] list <https://lists.mailman3.org/mailman3/lists/[email protected]/> -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
