![](https://secure.gravatar.com/avatar/1786350e8a814c84a91563c7c11e4000.jpg?s=120&d=mm&r=g)
On Tue, Aug 1, 2017, at 09:50 AM, Tom Browder wrote:
On Tue, Aug 1, 2017 at 12:28 Abhilash Raj <raj.abhilash1@gmail.com> wrote:>> Hi Tom, ....
On Tue, Aug 1, 2017, at 07:54 AM, Tom Browder wrote:
I'm leaning toward installing using the docker method but I would>> > appreciate any recent thoughts about which method to choose.
It really depends on what way you want to go, container images will be>> much less hassle to use right now, mostly because all the dependencies>> are bundled in and the moving parts are already configured to work with>> each other.
Abhilash, thanks for the response.
My goal is to use the installation in production immediately (production meaning using some interested friends as testers before opening lists to "real" subscribers).> If I understand properly, the docker way will be a good path to do that and it should make my volunteer maintenance life easier in the future, too.> Does that sound reasonable?
While other non-developers would be able to tell you more about how easy it is to administer these container images, I think I have made them easy easy as possible to deploy without having to worry about inner workings. Unless ofcourse you want something more customized, it should work Ok for you. I am planning to release some new bugfixes and enhancements very soon, maybe today or tomorrow depending on when can I get some time. That release should be a significant improvement over the current one with ease-to-use factor.
thanks, Abhilash Raj