search

alexyuen / duke

Automatically exported from code.google.com/p/duke
0 stars 0 forks source link

Support for deployment-independent configurations #72

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
It's a problem that the current Duke configuration mixes deployment-specific 
details in with the more general mapping and comparison setup. The actual 
server names, database names, user names and passwords will differ with the 
deployment environment, but the overall configuration is likely to remain the 
same.

In order to avoid having to create different XML files for different 
environments it should be possible to preload a duke.properties file that sets 
certain variables, which can then be referred to from the configuration file. 
Then one can have a single .xml file and several small .properties files.

Original issue reported on code.google.com by lar...@gmail.com on 9 Mar 2012 at 12:44

GoogleCodeExporter commented 8 years ago 
It would also be desirable to allow the configuration to be in different 
formats other then on disk.  Modifying the Configuration class to be an 
interface would allow different implementation to choose where to pull the data 
from.  

I would be willing to make this change and add support for yaml configuration 
files.  It would also allow implementations to offer other forms of 
configuration such as db etc.

Please let me know if you would like me to make the changes.

Phil

Original comment by phil...@helpscore.com on 19 Apr 2013 at 7:06

GoogleCodeExporter commented 8 years ago 
Phil, this is an interesting suggestion, but it's a separate issue, so I 
created issue 115 for it. Sorry to be so picky, but separating the issues makes 
things easier to keep track of.

Original comment by lar...@gmail.com on 20 Apr 2013 at 8:21