The configuration is written in the TOML format. It is loaded like this:

config/config.dist.toml

config/config.<branchname>.tomloptional

You can customize the configuration for the branch you are on in config/config.<branchname>.toml. The keys used in it, will override any values loaded from config/config.dist.toml. Without this configuration file, configuration will only come from config/config.dist.toml.

Update the ini files used by Pyramid: ./manuelini-files. You can check that the values in production.ini (contains database related configuration) and development.ini (imports the production.ini configuration file and contains development specific values) are correct.

If the command fails due to ImportError:Nomodulenamed'osgeo', check that the osgeo module from system install is available in the PYTHONPATH specificied in config/config.dist.sh. If not, create a config/config.sh with the correct value for PYTHONPATH. Eg for Debian, put this value:

In order to add a keyword, you must edit geo-api3/chsdi/customers/utils/search.py. If you edit the file on devel, then the keywords will be used for all customer (on next merge). If you edit it in a customer specific branch, then it will only be available for this customer.

To add a keyword, you must add a SearchKeywords namedtuple to the SEARCH_KEYWORDS tuple, like this:

git hooks allow you to launch a script before or after a git command. They are very handy to automatically perform checks. If the script exits with a non 0 status, the git command will be aborted. You must write them in the .git/hooks/ folder in a file following the convention: <pre|post>-<git-action>. You must not forget to make them executable, eg: chmod+x.git/hooks/pre-commit.

In the case you don’t want to launch the hooks, append the --no-verify option to the git command you want to use.