Re: [Discuss] - Cartridge Server Start - Extensions vs Plugins

2015-03-05 Thread Chamila De Alwis
Hi Imesh, +1. We'll use a new tag. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Thu, Mar 5, 2015 at 3:53 AM, Imesh Gunaratne wrote: > Hi Chamila, > > On Thu, Mar 5, 2015 at 2:11 AM, Chamila De Alwis > wrote: > >> Hi, >> >> I've opened a

Re: [Discuss] - Cartridge Server Start - Extensions vs Plugins

2015-03-04 Thread Imesh Gunaratne
Hi Chamila, On Thu, Mar 5, 2015 at 2:11 AM, Chamila De Alwis wrote: > Hi, > > I've opened a PR [1] for the initial implementation which includes the > server start plugins for the PHP and Tomcat docker images. Please review > and merge. After this, I will add the modifications necessary for the

Re: [Discuss] - Cartridge Server Start - Extensions vs Plugins

2015-03-04 Thread Chamila De Alwis
Hi, I've opened a PR [1] for the initial implementation which includes the server start plugins for the PHP and Tomcat docker images. Please review and merge. After this, I will add the modifications necessary for the Puppet modules and the Java Cartridge Agent to move the server start logic to t

Re: [Discuss] - Cartridge Server Start - Extensions vs Plugins

2015-03-03 Thread Imesh Gunaratne
+1 Yes a good point! We will need to start the servers based on the artifact repository availability. On Tue, Mar 3, 2015 at 2:50 PM, Chamila De Alwis wrote: > Hi, > > I've implemented a Python extension executor which would execute the bash > extensions files. The extension files are renamed t

[Discuss] - Cartridge Server Start - Extensions vs Plugins

2015-03-03 Thread Chamila De Alwis
Hi, I've implemented a Python extension executor which would execute the bash extensions files. The extension files are renamed to match their relevent event and a plugin called ExtensionExecutor will execute the extension based on the event it was triggered on. Since service start logic is now m