CloudServices/ServiceBuilder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= Overview = The '''Service Builder''' project is part of Project Sagrada , providing a tool for developers to create applications that follow Services stan...")
 
Line 31: Line 31:
* The tool generates a report with explanations for the next steps
* The tool generates a report with explanations for the next steps


See: https://bugzilla.mozilla.org/show_bug.cgi?id=674904


=== Phase 2 ===
=== Phase 2 ===

Revision as of 08:29, 30 September 2011

Overview

The Service Builder project is part of Project Sagrada , providing a tool for developers to create applications that follow Services standards.

Project

Engineers

  • Tarek Ziadé

User Requirements

Phase 1

The first version of Service Builder will be a simple command-line tool to generate a standard Python app via a wizard.

The generated app will be based on our framework (server-core) and will provide the boiler plate code and files that we need to build, release, deploy the application.

For the continuous integration aspect + DVCS, there will be no automated steps but what needs to be done after the app is generated, will be explained in detail:

- add a task in our Jenkins instance (semi-automated) - push the code in our github

The wizard will also provide a way to integrate in the application Sagrada libs

Requirements:

  • The tool is a one-shot call to create an application
  • The tool asks questions and generates the application
  • The tool generates a report with explanations for the next steps

See: https://bugzilla.mozilla.org/show_bug.cgi?id=674904

Phase 2

The second version of the project will provide a web application with the following features:

The developer will be able to:

  • add/edit projects via a Web UI or iPython
  • add/edit web services in every project, via a Web UI or iPython
  • add/edit his code, via a Web UI or iPython, or the file system with his usual editing tools
  • export/import projects so they are standalone applications like in phase 1.

Phase 3

The web application will be hosted in our infrastructure, and every developer will manage its webservices through it.