Project Home • Blog • Known Issues • External Project Link • Contact Project
EnvironmentConfig (EC) aims to solve a problem developers face when using multiple environments in the development lifecycle. That is that each server/environment may have properties that do not match the other servers. For instance, in a three tier development setup (development, staging and production) you may find that the data-source names (DSN’s), mail server address and credentials, path to certain folders, etc. differ from server to server. On each deployment or every time a patch is applied, the developer must ensure those variable properties are correct or else the application will break. Ensuring each environment contains the right values for each property may become a tedious process, especially if the application evolves constantly and/or the app resides in a clustered environment.
EnvironmentConfig address this issue by allowing the developers define each environment and properties in an XML file once. This file is processed when the application starts and EC will automatically detect the environment the application is running at, based on the domain name. The environment’s specific properties are loaded and available to the developer for use in a several ways depending on configuration set.
*** more details ***
You can use the properties returned by EC as a structure of properties (normal or flattened) or with a CFC that EC can create for you on the fly.
Another way to address this issue is using deployment scripts (e.g. ANT), but EnvironmentConfig makes it simpler and has other pros, like the ability to create a CFC with the properties on the fly and even generate the ColdSpring XML file for the CFC if you choose to.
Version 1.3 - Beta
Fixed multiple bugs (see listed below)
Added EnvironmentConfig API that allows you to leverage some of it's core methods in your own applications.
Bugs Fixed: RIA Forge Bug 2,3,4 & 5.
Read EC-ChangeLog.rtf in the documentation for more details.
To enter issues for this (or any other) project, you must be logged in.
Adobe and the Adobe product names are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.