On Fri, Apr 18, 2014 at 1:37 PM, Manuranga Perera <[email protected]> wrote:
> *Current Implementation* > We currently keep configuration files for jaggery apps within the app > itself (eg: site.json). > > *Issue with Current Implementation* > But this is creating some difficulties in multi environment deployments. > Since the configuration files will contain some environment specific > information (eg: SSO IDP URL), this makes the artifacts un-portable across > environments. > > *Suggested Solution* > We can implement a mechanism where the configuration is read from an > outside location (eg: repository/conf) at deployment time and keep it in > the application context and reuse it. > Or cant we create the configurations based on the environment at the startup maybe ? I assume you need to change the hostname/port etc right ? Regards, /Nuwan > > > Let's discuss the feasibility of this solution. alternative solutions are > welcome. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > -- *Thanks & Regards,* * Nuwan Bandara | Senior Technical Lead - Solutions Architecture, WSO2 Inc.+1 812.606.7390 | +1 650.745.4499 Ext 4210 | http://nuwanbando.com <http://nuwanbando.com> * <http://www.nuwanbando.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
