About The Project
Sometimes, we need to store config in our application that we don't want to expose to the public. For example, the database password, the api key, etc.
One solution is to store them in the OS' secret manager, such as Keychain on macOS, Credential Manager on Windows, libsecret on Linux.
However, they usually have limitation on the secret length. For example, Keychain only allows 255 bytes for the secret, Credential Manager is even shorter. So we can't store a long secret in it.
Another solution is to store the secret in a file and encrypt it with a rsa public key, and store the private key in the OS' secret manager. This is what this crate does.
In other cases, maybe our secret is not a String, but a config struct. We can also use this crate to manage it. When invoke [Config::get], it will deserialize the config from the cache and return it.
This crate provides 3 ways to manage your config:
- [
Source]: A normal source, not persisted or encrypted - [
PersistSource]: A source that will be persisted to local file, not encrypted - [
SecretSource]: A source that will be persisted to local file and encrypted
This crate also has some optional features:
persist: If enabled, you can use the [PersistSource].secret: If enabled, you can use the [PersistSource] and the [SecretSource] trait.mock: If enabled, you can use the mock for testing.derive: If enabled, you can use the derive macros to implement the [Source], [PersistSource] and [SecretSource] trait.default_config_dir: If enabled, the default config dir will be used. Implemented through dirs-next.protobuf: If enabled, protobuf will be used instead of json for better performance. (Not implemented yet)
Built With
- Rust
- Keyring
Usage
(You may see many #[cfg(feature = "...")] in the example below, if you are not familar to Rust, you may not know this attribute is for Conditinal Compile, so that I can test it in cargo test --all-features automatically to ensure all go right.)
You can implement the [Source], [PersistSource] and [SecretSource] yourself.
#
#
You can also use the derive macros.
#
#
For more examples, please refer to the Example or Documentation
Roadmap
- Enable protobuf instead of json for better performance
See the open issues for a full list of proposed features (and known issues).
Contributing
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
License
Distributed under the MIT License. See LICENSE.txt for more information.
Contact
Louis - 836250617@qq.com
Project Link: https://github.com/kingwingfly/encrypt-config