refactor: [#361] extract mod for configuration

src/bootstrap/app.rs

@@ -11,11 +11,11 @@
 //! 2. Initialize static variables.
 //! 3. Initialize logging.
 //! 4. Initialize the domain tracker.
-use std::env;
 use std::sync::Arc;
 
 use torrust_tracker_configuration::Configuration;
 
+use super::config::initialize_configuration;
 use crate::bootstrap;
 use crate::shared::clock::static_time;
 use crate::shared::crypto::ephemeral_instance_keys;
@@ -55,35 +55,6 @@ pub fn initialize_static() {
     lazy_static::initialize(&ephemeral_instance_keys::RANDOM_SEED);
 }
 
-/// It loads the application configuration from the environment.
-///
-/// There are two methods to inject the configuration:
-///
-/// 1. By using a config file: `config.toml`. The file must be in the same folder where you are running the tracker.
-/// 2. Environment variable: `TORRUST_TRACKER_CONFIG`. The variable contains the same contents as the `config.toml` file.
-///
-/// Environment variable has priority over the config file.
-///
-/// Refer to the [configuration documentation](https://docs.rs/torrust-tracker-configuration) for the configuration options.
-///
-/// # Panics
-///
-/// Will panic if it can't load the configuration from either
-/// `./config.toml` file or the env var `TORRUST_TRACKER_CONFIG`.
-#[must_use]
-fn initialize_configuration() -> Configuration {
-    const CONFIG_PATH: &str = "./config.toml";
-    const CONFIG_ENV_VAR_NAME: &str = "TORRUST_TRACKER_CONFIG";
-
-    if env::var(CONFIG_ENV_VAR_NAME).is_ok() {
-        println!("Loading configuration from env var {CONFIG_ENV_VAR_NAME}");
-        Configuration::load_from_env_var(CONFIG_ENV_VAR_NAME).unwrap()
-    } else {
-        println!("Loading configuration from config file {CONFIG_PATH}");
-        Configuration::load_from_file(CONFIG_PATH).unwrap()
-    }
-}
-
 /// It builds the domain tracker
 ///
 /// The tracker is the domain layer service. It's the entrypoint to make requests to the domain layer.

src/bootstrap/config.rs

@@ -0,0 +1,37 @@
+//! Initialize configuration from file or env var.
+//!
+//! All environment variables are prefixed with `TORRUST_TRACKER_BACK_`.
+use std::env;
+
+use torrust_tracker_configuration::Configuration;
+
+// Environment variables
+
+const CONFIG_PATH: &str = "./config.toml";
+const CONFIG_ENV_VAR_NAME: &str = "TORRUST_TRACKER_CONFIG";
+
+/// It loads the application configuration from the environment.
+///
+/// There are two methods to inject the configuration:
+///
+/// 1. By using a config file: `config.toml`. The file must be in the same folder where you are running the tracker.
+/// 2. Environment variable: `TORRUST_TRACKER_CONFIG`. The variable contains the same contents as the `config.toml` file.
+///
+/// Environment variable has priority over the config file.
+///
+/// Refer to the [configuration documentation](https://docs.rs/torrust-tracker-configuration) for the configuration options.
+///
+/// # Panics
+///
+/// Will panic if it can't load the configuration from either
+/// `./config.toml` file or the env var `TORRUST_TRACKER_CONFIG`.
+#[must_use]
+pub fn initialize_configuration() -> Configuration {
+    if env::var(CONFIG_ENV_VAR_NAME).is_ok() {
+        println!("Loading configuration from env var {CONFIG_ENV_VAR_NAME}");
+        Configuration::load_from_env_var(CONFIG_ENV_VAR_NAME).unwrap()
+    } else {
+        println!("Loading configuration from config file {CONFIG_PATH}");
+        Configuration::load_from_file(CONFIG_PATH).unwrap()
+    }
+}

src/bootstrap/mod.rs

@@ -6,5 +6,6 @@
 //! like cleaning torrents, and other jobs because they can be enabled/disabled depending on the configuration.
 //! For example, you can have more than one UDP and HTTP tracker, each server is executed like a independent job.
 pub mod app;
+pub mod config;
 pub mod jobs;
 pub mod logging;