It was also decided to look into the implementation details on How to handle the Git based Dep-Synch with normal cluster messaging (synchronize requests). Currently this skipped and ADC is used to send the messages.
On Thu, May 2, 2013 at 3:02 PM, Isuru Haththotuwa <[email protected]> wrote: > Two options were considered for the standard deployment of manager and > worker with Git based deployment synchronizer - > > 1. using a single repository with a branch created for each tenant > 2. using a repository per tenant > > From these approaches, it was decided that the #2 is the better one. #1 > option is complex, and the cleaner approach would be to use separate > repository for each tenant. From the code itself we should create the > different repositories for different tenants in a git server. As an > advanced use case, tenants can specify their own git repositories created > by them. > > Credentials for git repositories should be stored securely. We can use > Registry for this purpose. > > Consider the possibility of using puppet to create a git server to relieve > the user from configuring a git hosting mechanism (git server). > > Please add anything that I missed. > > -- > Thanks and Regards, > > Isuru H. > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
