Hi all, As a part of our effort to make the Appfactory support more
application types, we are going to facilitate PHP.

PHP support becomes important since it is one of the most popular
server-side scripting languages.

Appfactory would help the developers, QA engineers and other
stakeholders automate
and accelerate the application life-cycle management of their PHP web
applications.
Problem:

At the moment, PHP applications are not supported by Appfactory.
User story:

When user creates a php web application and performs application lifecycle
management operations on his application.

Application Creation:

1. A user navigates to ‘Create Application’ page.

2. Selects the application type as PHP Application.

3. Creates the application.

Application Deployment:

Subscription would be per-application, hence the following workflows.

1. Upon the deployment of the first version of an application onto a
particular stage, Appfactory would make a subscription in Stratos to the
PHP cartridge during the application creation (git repository containing
the web application artifacts is provided during the subscription).


Examples:


 a) A trunk version of the application is auto-built and auto-deployed onto
the ‘Development’ stage. Before the very first deployment happens (after
the auto build) Appfactory should make the subscription.


 b) Promotion of an application

e.g.

   -

   A developer promotes a particular version of an application from the
   Development stage to the Testing stage.
   -

   A QA Engineer clicks on the ‘Deploy’ button of that version.
   -

   Appfactory checks whether there is a subscription available for this
   application in Testing stage.
   -

   If there is no such subscription already, then Appfactory would make a
   new subscription.
   -

   Appfactory would deploy the particular application version onto the web
   server in the Test Stage.

 2. Any subsequent app versions deployed after the deployment of the first
version would use the same subscription if there is any subscriptions
available.


Optional/Improvements:

Demoting an application

e.g.

   -

   A QA engineer clicks the ‘demote’ button upon a test failure back to the
   dev stage.
   - If there are no versions available in the testing stage for that
   application, Appfactory would unsubscribe from the PHP cartridge.




-- 
Regards,

*Madhawa Bandara*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+94777487726*
Blog* - *classdeffound.blogspot.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to