Exposes a property affecting run-mode determination, for customisation.
Enumeration of available run modes.
When the run.mode
environment variable isn't set or recognised, this function is invoked to determine the
appropriate mode to use.
When the run.mode
environment variable isn't set or recognised, this function is invoked to determine the
appropriate mode to use.
This logic can be customised by calling set
before the run-mode is referenced. (An attempt to customise this
after the run-mode is realised will have no effect and will instead log a warning.)
Is the system running in development mode
The default run-mode auto-detection routine uses this function to infer whether Lift is being run in a test.
The default run-mode auto-detection routine uses this function to infer whether Lift is being run in a test.
This routine can be customised by calling set
before the run-mode is referenced. (An attempt to customise this
after the run-mode is realised will have no effect and will instead log a warning.)
Get the configuration property value for the specified key.
Get the configuration property value for the specified key.
key for the property to get
the value of the property if defined
The resource path segment corresponding to the system hostname.
Is the app running in the Google App engine (the System property in.
Is the app running in the Google App engine (the System property in.gae.j is set)
The mode for which to retrieve properties, retrieved by System.
The mode for which to retrieve properties, retrieved by System.getProperty("run.mode"). Recognized modes are "development", "test", "profile", "pilot", "staging" and "production" with the default run mode being development.
The resource path segment corresponding to the current mode.
Is the system running in production mode (apply full optimizations)
The map of key/value pairs retrieved from the property file.
Determine whether the specified properties exist.
Determine whether the specified properties exist.
the properties to test
the subset of strings in 'what' that do not correspond to keys for available properties.
Ensure that all of the specified properties exist; throw an exception if any of the specified values are not keys for available properties.
Is the system running in test mode
The list of paths to search for property file resources.
The list of paths to search for property file resources. Properties files may be found at either the classpath root or in /props
The resource path segment corresponding to the current system user (from System.
The resource path segment corresponding to the current system user (from System.getProperty("user.name"))
This is a function that returns the first places to look for a props file.
This is a function that returns the first places to look for a props file. The function returns a List of String -> () => Box[InputStream]. So, if you want to consult System.getProperties to look for a properties file or some such, you can set the whereToLook function in your Boot.scala file before you call anything else in Props.
Configuration management utilities.
If you want to provide a configuration file for a subset of your application or for a specific environment, Lift expects configuration files to be named in a manner relating to the context in which they are being used. The standard name format is:
with hostName and userName being optional, and modeName being one of "test", "staging", "production", "pilot", "profile", or "default". The standard Lift properties file extension is "props".