Environment Specific Configurations - Best practices

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Environment Specific Configurations - Best practices

Matthew Bertolini
I was wondering how everyone tackles environment specific configurations in OFBiz. We deploy the same codebase to multiple environments (local, development, QA, and production) and we have different settings for things like database connections, server settings, security settings, etc. What are the best practices for maintaining different settings for each environment?

In other Java applications I maintain, I have an environment variable (app.env) that I set a runtime with something like 'dev' or 'prod' which get used to load properties files named 'settings_dev.properties' and 'settings_prod.properties'. In the code (or in a spring file) can can substitute the ${app.env} with the environment name and it will load the correct configuration. Is something like this possible with OFBiz configuration/XML files? Is there a pre-baked solution already in place?

Thanks,
Matt Bertolini
Reply | Threaded
Open this post in threaded view
|

Re: Environment Specific Configurations - Best practices

Atul Vani
If it's data that is different, then you can have different ant readers.  
If it's the code or properties files, then you can maintain patches.

On Sat, 20 Apr 2013 02:31:16 +0530, Matthew Bertolini  
<[hidden email]> wrote:

> I was wondering how everyone tackles environment specific configurations  
> in OFBiz. We deploy the same codebase to multiple environments (local,  
> development, QA, and production) and we have different settings for  
> things like database connections, server settings, security settings,  
> etc. What are the best practices for maintaining different settings for  
> each environment?
>
> In other Java applications I maintain, I have an environment variable  
> (app.env) that I set a runtime with something like 'dev' or 'prod' which  
> get used to load properties files named 'settings_dev.properties' and  
> 'settings_prod.properties'. In the code (or in a spring file) can can  
> substitute the ${app.env} with the environment name and it will load the  
> correct configuration. Is something like this possible with OFBiz  
> configuration/XML files? Is there a pre-baked solution already in place?
>
> Thanks,
> Matt Bertolini


--
Using Opera's revolutionary email client: http://www.opera.com/mail/
Reply | Threaded
Open this post in threaded view
|

Re: Environment Specific Configurations - Best practices

Malin Nicolas
Hi Matt,

I manage all environnement with the addon manager.

I create a svn depot with generic configuration on a addon and all
environnement have a dedicate addon

Exemple :
  * site-configuration : contains all generic configuration for the
customer site (logo, smtp server, etc ..)
  * env-integration : contains all configuration for integration server
  * env-production : contains all configuration for production server
  * env-test : ... easy to find ! ;)
  * and so on

And when I deploy an ofbiz :
  * keep svn ofbiz version
  * adm install site-configuration
  * adm install ../local-patch/env-integration
  * ant build start

You can see http://code.google.com/a/apache-extras.org/p/ofbiz-adm/ for
detail

Nicolas

Le 20/04/2013 06:51, Atul Vani a écrit :

> If it's data that is different, then you can have different ant
> readers. If it's the code or properties files, then you can maintain
> patches.
>
> On Sat, 20 Apr 2013 02:31:16 +0530, Matthew Bertolini
> <[hidden email]> wrote:
>
>> I was wondering how everyone tackles environment specific
>> configurations in OFBiz. We deploy the same codebase to multiple
>> environments (local, development, QA, and production) and we have
>> different settings for things like database connections, server
>> settings, security settings, etc. What are the best practices for
>> maintaining different settings for each environment?
>>
>> In other Java applications I maintain, I have an environment variable
>> (app.env) that I set a runtime with something like 'dev' or 'prod'
>> which get used to load properties files named
>> 'settings_dev.properties' and 'settings_prod.properties'. In the code
>> (or in a spring file) can can substitute the ${app.env} with the
>> environment name and it will load the correct configuration. Is
>> something like this possible with OFBiz configuration/XML files? Is
>> there a pre-baked solution already in place?
>>
>> Thanks,
>> Matt Bertolini
>
>


--
Nicolas MALIN
Consultant
Tél : 06.17.66.40.06
Site projet : http://www.neogia.org/
-------
Société LibrenBerry
Tél : 02.48.02.56.12
Site : http://www.librenberry.net/