Mark Sapiro, Fri, Nov 04, 2005 at 08:41:07AM -0800:
> Having two 'live' mailman instances with separate data and keeping them
> synched would be very difficult.
Moving list configuration data to another backend system (ie something
different from python dbs) would be a big step forward. Aside from easier
backups and "offline" data manipulation it would transfer the job of
synching data to the underlying db architecture.
> Another approach which you can find discussed somewhat in the archives
> of this and/or the mailman-developers list is to have one live
> installation and a second 'hot spare' installation. Then the problem
> reduces to just keeping the spare's data current which is more
> manageable.
Another good solution (data can be synched by an external process - say,
a rather violent rsync). Anyway, as the externalization of the db tier,
this would leave the archives out of the game.
p.
--
pbm - "All stories are love stories."
(Robert McLiam Wilson - "Eureka Street")
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
