The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.


Tapper::Config - Tapper - Context sensitive configuration hub for all Tapper libs


 use Tapper::Config;
 say Tapper::Config->subconfig->{test_value};
 say Tapper::Config->subconfig->{paths}{build_conf_path};


Merges values from alternative config file locations into the config. This allows to overwrite values given from the config provided with the module. It searches for config in the following places. * /etc/tapper.cfg * $ENV{HOME}/.tapper/tapper.cfg * filename given in $ENV{TAPPER_CONFIG_FILE}

@param hash ref - config

@return hash ref - merged config

Environment merge

Depending on environment variables a context of life, test, or development is derived. Default is live. If HARNESS_ACTIVE is set the context is test, if TAPPER_DEVELOPMENT is set to 1 the context is development.

This context is used for creating the final config. Inside the config all keys under development or test are merged up into the main level. Therefore usually there you put special values overriding defaults.

Special entries

There are entries that are handled in special way:


This local path/file entry is prepended by the sharedir path of Tapper::Config to make it an absolute path.


When the environment variable TAPPERDBMS is set to postgresql (or mysql) then the config values for database.TestrunDB are overwritten by the values <database.by_TAPPERDBMS.postgresql.TestrunDB> respectively.

This introduces a backwards compatible way of using another DBMS with Tapper, in particular PostgreSQL.

These special entries are prepared after the default and context merges.


Return the actual config for the current context.


  • AMD OSRC Tapper Team <>

  • Tapper Team <>


This software is Copyright (c) 2018 by Advanced Micro Devices, Inc..

This is free software, licensed under:

  The (two-clause) FreeBSD License