*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. 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]
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
