-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement TOML Configuration for All Services #152
Conversation
a5320f7
to
9c11bd3
Compare
ea0be28
to
3cad8f0
Compare
eecfd30
to
b14fd10
Compare
16ea182
to
28a5f32
Compare
893953b
to
c422c91
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks great! I've left comments here and there, please, address the issues I've marked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
add config.toml around env variables fix docker build
934ce05
to
090dcc4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This pull request introduces a comprehensive implementation of TOML configuration for all services within the project.
The primary goal is to enhance configurability, ease of maintenance, and flexibility across various components.
The changes included in this pull request are outlined below:
Introduces TOML configuration file for all services.
Adopts TOML syntax for configuration file, providing a clear and human-readable format for specifying settings.
Defines services-specific settings in the configuration file.
Centralized configuration offers flexibility management for all services.
The configuration file supports the use of ENV variables, which greatly extends the possibilities.
Implements validation mechanisms to ensure that configuration files adhere to the expected structure and contain valid values. Introduces error handling for scenarios where configuration values are missing or incorrect.
For developers who want to operate the ReadRPC node for their own needs.
This PR includes serving the data related to specific contracts, which actsas a backend for applications.
The configuration provides opportunities not to serve all the archival data.
This pull request aims to enhance the maintainability and configurability of the project by adopting a standardized TOML configuration approach.