-
Notifications
You must be signed in to change notification settings - Fork 24
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
RFC: Client/Server Configuration #4
Comments
We should be consistent, and choose between underscore or dashes for naming ( |
The The idea is to use for example a directory where retrieve/store fetched files: $# ls /var/cache/luet/repos/
repo1/pkg1.tar
repo2/pkg2.tar
... Or in a LAN fetch packages from a node used as local cache mirrors that is integrated in this way:
The cached repository could be a feature of API Server instances. |
It seems that viper has an issue on parse structure from configuration files with field with an underscore (probably for the env key replacer):
I will rename |
This implement repositories integration b8f7122 |
Just to trace the implemented configuration file: https://github.com/mudler/luet/blob/develop/contrib/config/luet.yaml |
|
Integrate support of Viper/Cobra configuration for both client and build packages commands.
Format supported is YAML (or viper supported format):
Example of a configuration for the client:
List of repositories could be defined under the directory
/etc/luet/repositories.d/
in yaml:Example of repo1:
The text was updated successfully, but these errors were encountered: