For App Cloud scenarios, should we have the executable available for download from Settings? Another alternative is to have both the executable and source code referenced from the corresponding tutorial (which we need to be created by the way :))
And we need it to be preconfigured to run against App Cloud, and make sure it works against the cloud identity system. Also, might need to rename the executable for App Cloud - otherwise appfac might not be understood as the name. Dmitry P.S. I loved the video. Great way to present the results of work, and very impressive work creating the CLI tool itself! On Sun, Sep 13, 2015 at 5:51 PM, Fathima Dilhasha <[email protected]> wrote: > Hi Anuruddha, Manjula & Appfactory team, > > Thanks for all the support you gave to complete this successfully. > +1. I will send a pull request with the necessary updates. > > Thank You. > Regards, > Dilhasha > > Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> > (M.N.F.Dilhasha) > Undergraduate | Department of Computer Science and Engineering > University of Moratuwa > Sri Lanka > > On Thu, Sep 10, 2015 at 10:42 AM, Manjula Rathnayake <[email protected]> > wrote: > >> Hi Fathima, >> >> +1, Great job on the CLI tool. Lets release it with AF-2.2.0-M5 release >> as Anuruddha mentioned. >> >> thank you. >> >> On Thu, Sep 10, 2015 at 10:39 AM, Anuruddha Premalal <[email protected]> >> wrote: >> >>> Hi Fathima, >>> >>> Great work. We are looking forward to merge the CLI tool code the main >>> AppFactory repo. >>> >>> Can you send a pull request with necessary updates?. It's god if you >>> place the code under product-af/modules/tools. >>> >>> Also you'll have to update product distribution scripts and related pom >>> files to build the CLI tool when building the product. Since this >>> requires GO run-time to build, make sure to add a pre-requisite section to >>> the README. >>> >>> Regards, >>> Anuruddha. >>> >>> >>> On Sat, Aug 22, 2015 at 9:42 AM, Fathima Dilhasha < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> I have completed the main requirements for $subject. >>>> You can find a demo for the CLI Tool at [1] >>>> <https://drive.google.com/file/d/0B5jf9n7hxy8YV1VQMTJGZ3ZKeU0/view?usp=sharing> >>>> The presentation can be found at [2] >>>> <https://docs.google.com/presentation/d/1yNojFbikh09V57tMtcoaacyc_17Ev1xQrraQCBxjezY/edit?usp=sharing> >>>> Project Documentation can be found at [3] >>>> <https://docs.google.com/document/d/1bD9ouBR2HeDWQ-bmx7OxKQ9q8Km4u6S6UyqlFx0ASfQ/edit?usp=sharing> >>>> >>>> [1] >>>> https://drive.google.com/file/d/0B5jf9n7hxy8YV1VQMTJGZ3ZKeU0/view?usp=sharing >>>> [2] >>>> https://docs.google.com/presentation/d/1yNojFbikh09V57tMtcoaacyc_17Ev1xQrraQCBxjezY/edit?usp=sharing >>>> [3] >>>> https://docs.google.com/document/d/1bD9ouBR2HeDWQ-bmx7OxKQ9q8Km4u6S6UyqlFx0ASfQ/edit?usp=sharing >>>> >>>> There were few suggestions pointed out during the demo, >>>> -To make the base url configurable from the tool itself. >>>> -To add auto-complete functionality. >>>> >>>> I will work on these improvements as an extension of this project. >>>> Please point out any further suggestions. >>>> >>>> Thanks. >>>> Regards, >>>> Dilhasha >>>> >>>> >>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>> (M.N.F.Dilhasha) >>>> Undergraduate | Department of Computer Science and Engineering >>>> University of Moratuwa >>>> Sri Lanka >>>> >>>> On Thu, Jun 11, 2015 at 7:59 PM, Fathima Dilhasha < >>>> [email protected]> wrote: >>>> >>>>> Hi Anuruddha, >>>>> >>>>> Please find my suggestions in line. >>>>> >>>>> Regards, >>>>> Dilhasha >>>>> >>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>>> (M.N.F.Dilhasha) >>>>> Undergraduate | Department of Computer Science and Engineering >>>>> University of Moratuwa >>>>> Sri Lanka >>>>> >>>>> On Thu, Jun 11, 2015 at 4:51 AM, Anuruddha Premalal < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Fathima, >>>>>> >>>>>> Few questions. >>>>>> >>>>>> 1. What will be the command template for general and app specifics? >>>>>> >>>>> >>>>> My Idea of the command template is that both general and app >>>>> specific commands are treated the same way. I have added an attribute in >>>>> the command template named "validations". This validation will carry the >>>>> list of pre requirements for both type of commands. This way we don't >>>>> differentiate app specific commands and general commands during the >>>>> invocation. WDYT of that approach? >>>>> >>>>> >>>>>> 2. Are you going to treat both the command categories via the same >>>>>> CommandFactory? >>>>>> >>>>> >>>>> Depending on my suggestion for 1, I am planning to use the same >>>>> command factory. IMO, using different command templates and command >>>>> factories for the two types of commands introduces some extra effort to >>>>> recognize and categorize commands as general and app specific. WDYT ? >>>>> >>>>>> >>>>>> Suggestion. >>>>>> >>>>>> If the user executes app specific commands inside the app repository >>>>>> we can detect the app name by scanning the git remotes, that way users >>>>>> won't have to explicitly define the appname in the command. However we >>>>>> shouldn't limit appspecific command to be executed only within the app >>>>>> repo, 'cause there might be cases where users might need to trigger >>>>>> builds/ >>>>>> download logs even without the repo (considering a large repo) WDYT? >>>>>> >>>>> >>>>> We can define the different variations of the same command (i.e. for >>>>> app specific commands- when run within app repo or by explicitly defining >>>>> the app name) as separate commands, but link their implementation to be >>>>> the >>>>> same. WDYT? >>>>> >>>>>> >>>>>> Regards, >>>>>> Anuruddha. >>>>>> >>>>>> On Thu, Jun 4, 2015 at 1:02 AM, Fathima Dilhasha < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> In the spreadsheet at [1] >>>>>>> <https://docs.google.com/spreadsheets/d/1mq8wWlBjkDMmurfK7BZE3GvGlR2Fr8Gu7KcmahcKy2s/edit?usp=sharing>, >>>>>>> I have listed the requirements that need to be validated before each >>>>>>> command is executed. >>>>>>> Please update on any changes and corrections. >>>>>>> >>>>>>> [1] >>>>>>> https://docs.google.com/spreadsheets/d/1mq8wWlBjkDMmurfK7BZE3GvGlR2Fr8Gu7KcmahcKy2s/edit?usp=sharing >>>>>>> >>>>>>> Thanks. >>>>>>> Regards, >>>>>>> Dilhasha >>>>>>> >>>>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>>>>> (M.N.F.Dilhasha) >>>>>>> Undergraduate | Department of Computer Science and Engineering >>>>>>> University of Moratuwa >>>>>>> Sri Lanka >>>>>>> >>>>>>> On Thu, Jun 4, 2015 at 1:10 PM, Fathima Dilhasha < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I have come up with a design for rule based command execution in >>>>>>>> the CLI tool. Please find the attached class diagram. The basic idea >>>>>>>> is to >>>>>>>> have several implementations for the Command, so that all the available >>>>>>>> commands can be maintained in the command Factory. >>>>>>>> >>>>>>>> Your feedback and suggestions on this rule based approach are >>>>>>>> highly appreciated. >>>>>>>> >>>>>>>> Thanks. >>>>>>>> Regards, >>>>>>>> Dilhasha >>>>>>>> >>>>>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>>>>>> (M.N.F.Dilhasha) >>>>>>>> Undergraduate | Department of Computer Science and Engineering >>>>>>>> University of Moratuwa >>>>>>>> Sri Lanka >>>>>>>> >>>>>>>> On Thu, May 7, 2015 at 4:38 AM, Fathima Dilhasha < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Jasintha, >>>>>>>>> >>>>>>>>> Thank you for the valuable suggestions. I'll have a look at WSO2 >>>>>>>>> Developer Studio as well. >>>>>>>>> >>>>>>>>> Thanks. >>>>>>>>> Regards, >>>>>>>>> Dilhasha >>>>>>>>> >>>>>>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>>>>>>> (M.N.F.Dilhasha) >>>>>>>>> Undergraduate | Department of Computer Science and Engineering >>>>>>>>> University of Moratuwa >>>>>>>>> Sri Lanka >>>>>>>>> >>>>>>>>> On Tue, May 5, 2015 at 9:57 AM, Jasintha Dasanayake < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Similar functionalities have been implemented in the WSO2 >>>>>>>>>> Developer Studio, so you may refer[1] that as well,there you may >>>>>>>>>> find some >>>>>>>>>> useful API calls and logics too. >>>>>>>>>> >>>>>>>>>> Thanks and Regards >>>>>>>>>> /Jasintha >>>>>>>>>> >>>>>>>>>> [1] - >>>>>>>>>> https://github.com/wso2/developer-studio/tree/master/appfactory >>>>>>>>>> >>>>>>>>>> On Mon, May 4, 2015 at 5:10 PM, Fathima Dilhasha < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> As the initial step, I have come up with the following set of >>>>>>>>>>> basic functionalities to be implemented for AppFactory CLI tool >>>>>>>>>>> considering >>>>>>>>>>> CLI tools available for other platforms ( similar to App Factory ) >>>>>>>>>>> as well. >>>>>>>>>>> >>>>>>>>>>> *General Commands* >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> - list supported commands >>>>>>>>>>> - manage app creation and deletion >>>>>>>>>>> - list App details >>>>>>>>>>> - authentication to App Factory (login, logout) >>>>>>>>>>> - API Management (listing API keys) >>>>>>>>>>> - Database/Data source management >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> *Application Specific Commands* >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I think there should be command to list the all application >>>>>>>>>> first, then should be a command to get information for a select >>>>>>>>>> application. >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> - List information about Application >>>>>>>>>>> - Life Cycle Management for an aplication >>>>>>>>>>> - Display logs for an application >>>>>>>>>>> - Manage App versioning >>>>>>>>>>> - Application User Management >>>>>>>>>>> - Get Latest Build Info for app >>>>>>>>>>> >>>>>>>>>>> This tool will take use of system native shell rather than a >>>>>>>>>>> separate App Factory specific shell. This approach is expected to >>>>>>>>>>> provide >>>>>>>>>>> better user experience. The tool will be built in 'GO' since it >>>>>>>>>>> caters for >>>>>>>>>>> easy adoption to different OSs with cross compilation support, easy >>>>>>>>>>> integration of functionalities into system native shell. >>>>>>>>>>> >>>>>>>>>>> Your feedback and suggestions on this approach are highly >>>>>>>>>>> appreciated. >>>>>>>>>>> >>>>>>>>>>> Thanks. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Dilhasha >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>>>>>>>>> (M.N.F.Dilhasha) >>>>>>>>>>> Undergraduate | Department of Computer Science and Engineering >>>>>>>>>>> University of Moratuwa >>>>>>>>>>> Sri Lanka >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Architecture mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> *Jasintha Dasanayake* >>>>>>>>>> >>>>>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>>>>>>>> <http://wso2.com/>lean . enterprise . middleware* >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *mobile :- 0711368118* >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Architecture mailing list >>>>>>>>>> [email protected] >>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Anuruddha Premalal* >>>>>> Software Eng. | WSO2 Inc. >>>>>> Mobile : +94710461070 >>>>>> Web site : www.regilandvalley.com >>>>>> >>>>>> >>>>> >>>> >>> >>> >>> -- >>> *Anuruddha Premalal* >>> Software Eng. | WSO2 Inc. >>> Mobile : +94710461070 >>> Web site : www.anuruddha.org >>> >>> >> >> >> -- >> Manjula Rathnayaka >> Associate Technical Lead >> WSO2, Inc. >> Mobile:+94 77 743 1987 >> > > -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware <http://wso2.com/events/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
