Download

From Open Web Analytics Wiki

Jump to: navigation, search

Contents

Subversion Access

The easiest way to get the latest OWA code is to do checkout of the trunk from OWA subversion (SVN) repository. All you need is a Subversion client which is install on most UNIX hosts these days.

You can browse the Subversion repository at http://svn.openwebanalytics.com/owa .

The repository contains three top level directories:

Checking Out Code

To check out code from the repository follow these steps:

  1. navigate to the directory on your server that you want Subservion to check out code into. On a UNIX host this is something like:
    cd your_dir
  2. Then type the following command:
    svn co http://svn.openwebanalytics.com/owa/WHAT/ ./owa
    "WHAT" is the name of the directory path in the repository that you would like to check out. For example to check out the trunk you would type:
    svn co http://svn.openwebanalytics.com/owa/trunk/ ./owa
    To check out the v1.0 branch you would type:
    svn co http://svn.openwebanalytics.com/owa/branches/1.0/ ./owa

Updating Your Copy of the Code

To update your copy of code of the code follow these steps:

  1. Navigate to the directory on your server where you checked out the code
  2. Type the following SVN command:
    svn update

This will only update files contained in subversion, meaning that any new files that you created (like your configuration file, or new plugins that you create) will remain untouched. However it does mean that if you modified one of the core OWA files that you will need to manually merge your changes.

Distributions

Package Downloads

You can download the latest releases by pointing your web browser or HTTP client at: http://downloads.openwebanalytics.com/owa

Subversion

All version of the code are housed in the Subversion repository. Major releases have their own home in the branches directory. Major release branches enjoy updates whenever minor releases occur so that one can simply svn update off of that directory untill there is a new major release. For example /owa/branches/1.0 will have 1.0.1 and 1.0.2 merged into it as those minor releases happen. If a release involves a major schema change, it will probably be branched as a major release.

In addtion to the branches, all releases major or minor will be stored in the tags directory if you ever need to roll back to a specific release.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox