Allows to have properties configuration files outside of the war
For now, the root directory where properties files are search by Props is not configurable and is in the classpath (at root level or under /props/ directory).
We need to be able to specify file system directory, for example to put application configuration files under a usual path for admin sys, for example under /etc/MyApp/ on unix.
The path could be configured via a JVM parameter, for example: -Dlift.props.path=/foo/bar/baz
BUT this would be problematic with several Lift application running in the same container.
More information in mailing list thread: http://groups.google.com/group/liftweb/browse_frm/thread/69c7fa887905a5c5
We need to be able to specify file system directory, for example to put application configuration files under a usual path for admin sys, for example under /etc/MyApp/ on unix.
The path could be configured via a JVM parameter, for example: -Dlift.props.path=/foo/bar/baz
BUT this would be problematic with several Lift application running in the same container.
More information in mailing list thread: http://groups.google.com/group/liftweb/browse_frm/thread/69c7fa887905a5c5
Leave a comment
(In revision:8eb0c6a0273decc5b863a9228568fd8411a94235) Closes #571. Allows the user to insert a function that searches around for properties files outside of Lift's normal props file locations
Branch: master
Branch: master