Replies: 2 comments
-
If you are talking about config files, yes, for different setups you need different config files. But you can put common options in another config file, e.g. `common.toml` and source them using `use-profile = ["common"]`. Note that you can source from multiple other profiles and even do so recursively, i.e. you could also use a `use-profile` within `common.toml`.
Another remark which might help in your setup: Have a look at the `copy` command which can be used to copy snapshots to another repository.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Oh, just forgot: Of course, you can also have multiple config files and use them all with the CLI, e.g. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm backup up the same (or at least similar) data to a local HD and to a cloud server. If I read the config files right, this would mean I need one for the cloud and one for local, even though they share some parameters. Do you think it would be possible to have some way to backup the same sources to different repositories with less duplication?
Bonus if the forget rules could change based on the repo, too - locally, I keep backups for much longer than in the cloud.
Beta Was this translation helpful? Give feedback.
All reactions