One of the tenets of a Twelve-Factor app is to store application configs in the environment the application is deployed to. To pass config values t...
For further actions, you may consider blocking this person and/or reporting abuse
I liked the usage of the dotenv crate for reading config values from a .env file. It simplifies the process and makes it more organized for different environments.
While I found the article informative, I wish it had included more advanced techniques or real-world examples of managing complex configurations in Rust applications...
finally a clear and solution to managing configs in rust! Ive been struggling with it. The ConfigProvider trait idea is brilliant for handling different sources.
i enjoyed this article, very informativea nd well structured
The explanation of reading from environment variables is useful, especially for containerized applications. Good to know that Rust's standard library can handle it without extra crates.
I can already tell that the section on reading from command line arguments using argmap is going to save me a lot of time.
good intro, but I would have liked a deeper dive into advanced scenarios like dynamic config reloading or integration with configuration management tools.
good, easy to undestand read! lots of helpful advice
The use of the expect() method for mandatory config values is a good practice! It ensures that the application won't start if critical config data is missing.
would have liked to see more about handling secret or sensitive configuration data securely. a good starting point though
this was very helpful, thanks
I found the article well-structured and easy to follow. Nicealy done
a great guide for managing application configs in Rust. the explanation of reading from environment variables was very helpful for my project.
the section on reading from command line arguments really helped with my project. straightforward and effective!