We will be using both ServerHome/deployment and
ServerHome/wso2/{runtime}/deployment directories. Please refer to
architecture mailing list[1][1] - [Architecture] Multiple runtime support for C5 based products Thanks Thusitha On Wed, Mar 8, 2017 at 5:49 PM, Niranjan Karunanandham <[email protected]> wrote: > Hi All, > > As per the offline discussion with Azeez, it was suggested that the > deployment folder should be per runtime. > > Regards, > Nira > > On Mon, Mar 6, 2017 at 10:47 AM, Imesh Gunaratne <[email protected]> wrote: > >> Thanks for the quick response Niranjan! >> >> On Mon, Mar 6, 2017 at 9:40 AM, Niranjan Karunanandham <[email protected] >> > wrote: >> >> >>> Would we have deployment artifacts which can are required by all the >>> runtime? In which case should the artifact be in each runtime as in [1] or >>> will we be having it [2] which deploys for all runtime? >>> >> >> β+1 Yes, it would be better to place common deployable artifacts at the >> root level to avoid duplication. Otherwise, users would need to update the >> same set of files at multiple locations when working with this distribution. >> >>> >>> In <CARBON_HOME>, we have bin (which should contain the script to start >>> all runtime), dbscript, resources which contain the keystores (JKS) and >>> logs (IMO the logs should be per runtime). >>> >> >> βIt make sense! Anything common to multiple runtimes can reside at the >> root level.β >> >> As we discussed offline, I think it might be better to ship separate >> distributions for runtimes together with the all-in-one distribution. >> Otherwise users would need to create separate distributions for runtimes >> when those need to be deployed separately. This would be necessary when >> creating container images, container cluster manager artifacts (Docker >> Swarm, K8S, DC/OS, etc), configuration management modules (Chef, Puppet, >> etc), etc as those would map one to one to each process. >> >> Thanks >> Imesh >> >>> >>> >>> >>>> >>>> Thanks >>>> >>>> >>>>> Regards, >>>>> Nira >>>>> >>>>> -- >>>>> >>>>> >>>>> *Niranjan Karunanandham* >>>>> Associate Technical Lead - WSO2 Inc. >>>>> WSO2 Inc.: http://www.wso2.com >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Imesh Gunaratne* >>>> Software Architect >>>> WSO2 Inc: http://wso2.com >>>> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057> >>>> W: https://medium.com/@imesh TW: @imesh >>>> lean. enterprise. middleware >>>> >>>> >>> Regards, >>> Nira >>> >>> -- >>> >>> >>> *Niranjan Karunanandham* >>> Associate Technical Lead - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >>> >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057> >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > > -- > > > *Niranjan Karunanandham* > Associate Technical Lead - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thusitha Dayaratne WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com About http://about.me/thusithathilina <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
