I know. I'm simply pointing out we already use Gitblit --- so please use that rather than add another different dependency. Unless of course there is a good reason to use a different git server, in which case we will look at the other one.
Paul On 25 July 2013 05:12, Isuru Haththotuwa <[email protected]> wrote: > On Thu, Jul 25, 2013 at 1:20 AM, Paul Fremantle <[email protected]> wrote: > >> We are already shipping gitblit with the S2 demo AMI. >> > > This is not S2 specific. > >> >> Paul >> >> >> On 24 July 2013 15:16, Isuru Haththotuwa <[email protected]> wrote: >> >>> Hi, >>> >>> In the git based deployment synchronizer, we have a repository per >>> tenant. Therefore we need to create git repositories dynamically for the >>> tenants created. For this we need to communicate with the relevant git >>> server at the runtime through a java api. Came across two commonly used git >>> servers, Gitblit [1] and SCM Manager [2]. I implemented support for GitBlit >>> to test the component and I'm in the process of implementing support for >>> SCM Manager. WDYT of these options as Git servers for Git based deployment >>> synchronizer? >>> >>> [1]. http://gitblit.com/ >>> [2]. http://www.scm-manager.org/ >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Paul Fremantle >> CTO and Co-Founder, WSO2 >> OASIS WS-RX TC Co-chair, Apache Member >> >> UK: +44 207 096 0336 >> US: +1 646 595 7614 >> >> blog: http://pzf.fremantle.org >> twitter.com/pzfreo >> [email protected] >> >> wso2.com Lean Enterprise Middleware >> >> Disclaimer: This communication may contain privileged or other >> confidential information and is intended exclusively for the addressee/s. >> If you are not the intended recipient/s, or believe that you may have >> received this communication in error, please reply to the sender indicating >> that fact and delete the copy you received and in addition, you should not >> print, copy, retransmit, disseminate, or otherwise use the information >> contained in this communication. Internet communications cannot be >> guaranteed to be timely, secure, error or virus-free. The sender does not >> accept liability for any errors or omissions. >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thanks and Regards, > > Isuru H. > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
