You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a restic rest dedicated backup server that hosts multiple repositories. I am just playing around with building my first .autorestic.yml and it seems that anchors and aliases would work great if I could split the scheme, hostname, and domain, from the repository path. Then for each repository, all I would need to override would be the path section, and the key (which comes from a .env file or environment variables anyway. At present, all I can use the YAML aliases for is the type, and the rest user and password (which should also be available through the .env file for security purposes.
I have a restic rest dedicated backup server that hosts multiple repositories. I am just playing around with building my first
.autorestic.yml
and it seems that anchors and aliases would work great if I could split the scheme, hostname, and domain, from the repository path. Then for each repository, all I would need to override would be the path section, and the key (which comes from a.env
file or environment variables anyway. At present, all I can use the YAML aliases for is the type, and the rest user and password (which should also be available through the.env
file for security purposes.An example presently:
What I'd like to be able to do is:
This would allow efficient use of YAML aliases to specify, for each repository, as distinct backends, just the path, and key.
The text was updated successfully, but these errors were encountered: