Hi. I currently have a single shiro.ini file checked into source control. Some of the parameters set in the file, however, such as the database connection and keys, differ across different environments: production, Q/A, staging, and production. As a result, I currently need to manually change the shiro.ini file during deployments to each environment. This is error-prone and reduces automation and scalability.
An alternative would be not to have shiro.ini checked into source control, but stored locally in each environment. But then changes to the file would still have to be manually carried across to each environment, with similar problems. Since we are in active development, that can be often. Is there a way to specify different environments for portions of the shiro.ini file? (Somewhat like Maven?) If not, what are recommended best practices that people use to handle this situation? Thanks for any advice! -- View this message in context: http://shiro-user.582556.n2.nabble.com/Best-practice-for-managing-different-shiro-ini-files-for-different-environment-tp7579099.html Sent from the Shiro User mailing list archive at Nabble.com.
