Re: Proposal for structure the incubator-mfa-server subtree.

[Brian Spector <br...@qredo.com>]

Hi Giorgio, thanks for this.


Could you please review and comment on the blog post I created and the email I just send out.

https://cwiki.apache.org/confluence/display/MILAGRO/2019/06/01/Updating+Milagro

I know Stan has a lot of thoughts about how we should package up an updated, modern deployable Milagro Server.

My vision is that we should have some sort of install script that can easily deploy the right components into the server depending on the type (or role) the server is performing.

As an example, if you are running in D-TA mode, this might be a different config that an authentication server, or a crypto custody server.

If we can incorporate your M-Pin auth specific ideas into this framework, that would be ideal.

Brian
________________________________
From: Giorgio Zoppi <gi...@gmail.com>
Sent: 31 May 2019 7:58 PM
To: dev@milagro.incubator.apache.org
Subject: Proposal for structure the incubator-mfa-server subtree.

Dear all,
i would like to begin the discussion of the proposal of the subtree
mfa-server.
My idea is to separate the tests and in src in two separate folders and as
well the python and ongoing cpp work.
An possible structure, might be:
*./src # source directory*






*./test # test directory./deprecated # deprecated stuff (in case of
mfa-server) is not needed../src/cpp # c++ code./src/python    # python
tornado server./test/cpp      # catch/gtest for c++ code./test/python   #
nose or current tests for python tornado server../examples # here we can
put an demos application.*

*./docker      # any docker description *

*./build         # any binary package (deb/rpm/exe)*
The same structure can be thought for the library or something similar to
Apache Mxnet since it is a project that supports multiple languages..
I will help to restruct any structure that come from this discussion.

Best Regards,
Giorgio