Building and maintaining customized versions of OpenPetra

Purpose

Every organisation is different, so there cannot be one OpenPetra installation for all. It might work for smaller charities, for one country, but for bigger offices the default version of OpenPetra is not sufficient.

There must be a standard way to accomplish this, which will ensure that updates from upstream can be used in the customized version, and local improvements can be merged back into upstream if they would benefit other organisations as well.

Build files

• The default config file for OpenPetra.build is stored in eg. OpenPetra.build-sample-win.config
• Usually, the file is copied to OpenPetra.build.config, and that file is not committed to the repository, since every developer will have different settings in that file.
• For a defined environment in an organisation or if the repository is only used by one developer, you can commit the file OpenPetra.build.config.my to your local repository, which will be picked up instead of OpenPetra.build.config

Configuration files

• The default configuration files are stored in the format Client.config.sample.
• Customized configuration files should be stored in the format Client.config.my, and will be picked up by the nant tasks which build the installers.

Navigation files

TODO

Translation files

TODO

Plugins

TODO