This results in Rocket preferring the values in the ROCKET_PROFILE profile. For example, with the default provider, you can set the selected profile via ROCKET_PROFILE. Rocket's Config and Config::figment() providers automatically set the configuration profile to "debug" when compiled in "debug" mode and "release" when compiled in release mode, but you can arbitrarily name and set profiles to your desire. Profiles #Ĭonfigurations can be arbitrarily namespaced by Profiles. * Note: the workers, max_blocking, and shutdown.force configuration parameters are only read from the default provider.
Whether ctrl-c initiates a server shutdown. Secret key for signing and encrypting values. Whether to use colors and emoji when logging. Keep-alive timeout seconds disabled when 0.
ROCKETDOCS HEADQUARTERS HOW TO
If and how to identify via the Server header. Limit on threads to start for blocking tasks. Number of threads to use for executing futures. This means that no matter which configuration provider Rocket is asked to use, it must be able to read the following configuration values: Rocket expects to be able to extract a Config structure from the provider it is configured with.
Providers can be combined into a single Figment provider from which any configuration structure that implements Deserialize can be extracted. Rocket's Config and Config::figment(), as well as Figment's Toml and Json, are some examples of providers. Rocket's configuration system is based on Figment's Providers, types which provide configuration data. Based on Figment, it allows you to configure your application the way you want while also providing with a sensible set of defaults. Rocket's configuration system is flexible.
0 kommentar(er)
