On Mon, 17 Aug 2020 at 10:16, sebb <[email protected]> wrote: > > I notice that the only tool that has been ported to ponymail-foal is > archive.py (and setup.py). > > However rather than porting elastic.py and ponymailconfig.py, > archive.py does its own config checking and database setup. > > Why is this?
Sorry, I see now that archiver.py was never converted to use the elastic.py interface. I thought I had done all the tools. However it would still make sense to use the standard config access, suitably modified for yaml. There would have been no need to convert the config calls in the original code, making it easier to see what has actually changed. > S.
