Powered By

  • OpenWGA Blogs 2.4.2 Build 132
    Running on:
    womodo CMS Server 7.8.4 Maintenance Release (Build 696)

Development in Teams

Most CMS products do not really support developer teams:
Templates are edited on a shared file system on a central development server. When saving a template from your editor you can't avoid overwriting changes other developers made in the meantime on the same file. If your template does not work as expected other developers may be disturbed because they are working on the same development server.
In addition to all that pain the developers suffer you need to install and maintain one development server for each customer you work for leading to a complex and expensive server infrastructure.
Why not let the developer work locally on his workstation and share template code through code repositories like SVN or CVS? The project manager could then check out the latest code changes on his workstation, approve it, tag this revision in the repository and update the production server with that code revision.

We can only guess why most CMS do not support that way to develop in teams.
May be the server installation process is too complex to do it on each workstation?
May be the server configuration itself is too complex to do it on each workstation and to ensure that each developer uses the same config?

What ever the reasons are: OpenWGA lets you work in exactly the way described above.

Installing a local OpenWGA development system on a workstation is done in two easy steps:
  • Install the OpenWGA Developer Studio.
    This is as easy as unpacking a zip file on your workstation and start the OpenWGA IDE.
  • Create a OpenWGA CMS runtime inside the OpenWGA Developer Studio.
A "runtime" is your local CMS system you work with.
You may create as many runtimes as you like. Typically you create one runtime for each customer you work for. A runtime does not only contain your template code. It also contains the complete configuration of your local CMS system: configured database servers and databases, authoring systems, language settings, used plugins, additional JARS and even information about the OpenWGA version you develop the project for.
You can checkin the complete runtime with all the templates and server configuration into the code repository where other developers can check them out and start working in exactly the same environment as you work in.
When a project is finished you can safely delete the runtime from your workstation if you want. When ever you need to reactivate the project you just have to checkout the runtime from SVN/CVS and start working in the same environment you left the project.

Enter Your Comment:

use markdown syntax