AppConfig is a small application configuration library to provide properties for applications deployed to different environments.


First, do a static import AppConfig.p(...) method:

import static org.javalite.app_configAppConfig.p;

then, simply call a statis p(..) method in places where you need to inject a property:

String name = p("name");


AppConfig allows configuration of applications that is specific for different deployment environments. Applications could have environment-specific files, whose names follow this pattern:, where environment is a name of a deployment environment, such as development, staging, production, etc.

You can also provide a global file, properties from which will be loaded in all environments:

In all cases the files need to be on the classpath under directory/package /app_config.

Environment-specific file will have an "environment" part of the file name match to an environment variable called ACTIVE_ENV. Such configuration is easy to achieve in Unix shell:

export ACTIVE_ENV=test

Typical file structure


Global property file will always be loaded, while others will be loaded depending on the value of ACTIVE_ENV environment variable.

If environment variable ACTIVE_ENV is missing, it defaults to development.

System property override

You can also provide an environment as a system property

Here is an example (add this to the startup script for your app):

The system property points to a file specific to that computer (local box, server, etc.). If a specific property is provided in the properties file loaded on classpath, and the same property is also found in the file, then the value loaded from a local file overrides the one loaded from classpath.

How to comment

The comment section below is to discuss documentation on this page.

If you have an issue, or discover bug, please follow instructions on the Support page