On Wed, Oct 28, 2020 at 11:31:49AM +1100, Daniel Axtens wrote: > > I think we may be oversetimating how many people out there run > > patchwork. :) My general concern was to make sure that parsemail doesn't > > do things like clear django data. If, to your knowledge, all it does is > > write to the database without interacting with the running process, then > > there's no reason why the feeder and the consumer can't live on > > different systems. > > Yeah, Patchwork sits in this really weird space where there are not many > deployments, but still too many for us to deeply integrate with any > one site's infrastructure/setup. It also means that we don't have direct > access to a copy of any site's data, which regularly bites everyone when > we write inefficient migrations.
I can make available the data from https://lore.kernel.org/patchwork -- that's a "read-only" patchwork with LKML sources that is only modified by the patchwork-bot and no actual developers. It uses postgresql as the backend, so it would be easy for me to provide a full DB dump for tests without any privacy concerns. -K _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
