Skip to content
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

Changes to rustic config #1125

Open
simonsan opened this issue Apr 18, 2024 · 0 comments
Open

Changes to rustic config #1125

simonsan opened this issue Apr 18, 2024 · 0 comments
Labels
A-config Area: Related to the config file functionality and format A-ui-ux Area: Related to user interfaces and user experience C-enhancement Category: New feature or request C-refactor Category: Refactoring of already existing code

Comments

@simonsan
Copy link
Contributor

simonsan commented Apr 18, 2024

I think it might be also confusing to have [[backup.sources]] multiple times and then to have a field called source which takes multiple values again.

The field should probably be renamed to sources and the table name to [[backup.source-groups]] or something. So it's clearer. Then sources takes an array of paths: ["/path/1/2", "path/3/4"].

Originally posted by @simonsan in #1094 (comment)

@simonsan simonsan added A-config Area: Related to the config file functionality and format A-ui-ux Area: Related to user interfaces and user experience C-enhancement Category: New feature or request C-refactor Category: Refactoring of already existing code labels Apr 18, 2024
@github-actions github-actions bot added the S-triage Status: Waiting for a maintainer to triage this issue/PR label Apr 18, 2024
@simonsan simonsan changed the title I think it might be also confusing to have [[backup.sources]] multiple times and then to have a field called source which takes multiple values again. Changes to rustic config Apr 18, 2024
@simonsan simonsan removed the S-triage Status: Waiting for a maintainer to triage this issue/PR label Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-config Area: Related to the config file functionality and format A-ui-ux Area: Related to user interfaces and user experience C-enhancement Category: New feature or request C-refactor Category: Refactoring of already existing code
Projects
None yet
Development

No branches or pull requests

1 participant