On Wed, Sep 27, 2017, at 10:29 AM, Dmitry Makovey wrote:
On 09/27/2017 10:20 AM, Abhilash Raj wrote:
On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote:
On 09/27/2017 08:26 AM, Dmitry Makovey wrote:
On 09/27/2017 08:25 AM, Dmitry Makovey wrote:
I've come across mailman-cli docs:
http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/using...
This is basically one of our GSoC projects which hasn't yet been merged with MailmanClient. It uses the REST API to to provide a command line client for Mailman, while there hasn't been any in-compatible changes in API since this project was finished, I am not sure about the current status of it.
yet I cannot figure out what's the official source for the installation.
Official source for MailmanClient is at gitlab.com/mailman/mailmanclient and it doesn't have a CLI, the Github project you linked to says right on the top that it is not official project (Thanks for that Rajeev!).
I did see that, thus I was asking the question here.
Also, I would say not to use this client to remotely access Mailman, the REST API is not meant to be exposed over internet (unless you have a VPN or other sort of setup to securely access the box remotely).
in my case - I need to use REST API since we're deploying with docker and pieces that need to integrate with mailman commands now live in a different container (and very likely on a different machine). I do need to be able to execute commands remotely - I can handle securing of that connection, but it is not an option for me to run "fat" docker containers thus the only interconnect is via sockets (either UNIX or TCP).
The CLI project is basically a Shell+CLI based on MailmanClient (python library for Mailman API) and Mailman Core's REST API. So, if I understand correctly, this would run commands over REST API like you want.
-- Abhilash Raj maxking@asynchronous.in