I
To be honest, I lack professional experience as a programmer. Currently I use linux/open source to advance my (and my community’s) digital rights and capacity, learning on ad hoc basis as I deal with personal computing needs. It’s only during my introduction to restic that I’ve come to a basic understanding of environment variables. I might not ever gain an overall understanding of how different frameworks for programming variables fit together!
I received restic forum advice from @dionorgua - see Fatal: Unable to Save Snapshot - suggesting I move the cache location to a larger filesystem by using this flag.
I think it’s too small. Consider using --cache-dir option with restic to move cache to some other place…
When I looked up this restic documentation
- Backing up — restic 0.16.3 documentation
- Manual — restic 0.16.3 documentation
- Manual — restic 0.16.3 documentation
There was nothing explicit about the flag only affecting current command, or about how to change the default cache location for a whole terminal session, or permanently. Yes, the caching section of the manual says:
The cache is automatically created, usually in an OS-specific cache folder:
- Linux/other:
~/.cache/restic(or$XDG_CACHE_HOME/restic)
but I lacked the background knowledge to understand this meant $XDG_CACHE_HOME was an environment variable that could be set for a whole session/script.
Restic seems to be a fantastic tool, and well-supported by you and your partners. I’ve made my suggestions regarding the documentation because there seems to be a number of restic users with a command line skill-base similar to my own, who would benefit from the proposed changes. Thanks for responding 