| Version 7 (modified by , 17 years ago) (diff) |
|---|
How to Install QWG Templates
TracNav
Table of Contents
Note : QWG templates are intended to work both with original CVS-based CDB and the new Subversion-based SCDB. But their integration has been tested mainly with SCDB and tools described here applies mainly to SCDB. Report any problem you could encounter with original CDB.
Initial Installation
For an initial installation of QWG templates, you first need to initialize you repository with a base configuration database. If you want to use SCDB, you need :
- Setup basic structure of SCDB.
- Export QWG templates (e.g. use
svn exportor download the tarball) in your SCDB.
Upgrading an existing repository
If you are using the recommended template layout with separate areas for standard templates in your configuration database, upgrading should be no more than replacing the previous version of the templates.
We do our best to ensure that new versions are backward compatible. This means that if you made site customization using the described method (pro_lcg2_config_site, pro_site_cluster_info...) and didn't modify standard templates, no changes should be required to use new version of the templates. When this is really required to introduce a new feature or bring more flexibility for configuring a service, it can happen that this full compatibility cannot be retained. This is normally stated in release announcement. You are always better to check...
For an easy upgrade, the recommended method is :
- Checkout the QWG template branch you need, in a separate area from your configuration database.
- Synchronize your configuration database with your local copy of QWG templates.
To integrate new/changed templates in your configuration database, you can use the tool documented at Development/RepUpdate?, originally developped to do the reverse synchronization (update QWG repository from a real configuration database). This tool can be used only with SCDB, as it relies on Subversion to do a non destructive update. As a benefit, it cannot damage your configuration database as every change made by this tool can be reverted with Subversion.
