Skip to content

Add possibilty to use a cache#33

Merged
aawsome merged 5 commits intomainfrom
add-cache
Jul 1, 2022
Merged

Add possibilty to use a cache#33
aawsome merged 5 commits intomainfrom
add-cache

Conversation

@aawsome
Copy link
Copy Markdown
Member

@aawsome aawsome commented Jun 26, 2022 •
edited
Loading

Open points are:

  • update Readme
  • Add checks for cache in check command
  • remove unneeded tree packs when reading the index

If a cache base dir is not explicitely given, rustic first tries to find a restic cache dir for the given repo and uses this one exists. If not, it searches for a rustic cache dir.

@aawsome aawsome force-pushed the add-cache branch 2 times, most recently from 4a6de7a to fe183ca Compare June 28, 2022 07:11
@aawsome aawsome changed the title Add cache Add possibilty to usa a cache Jun 28, 2022
@aawsome aawsome changed the title Add possibilty to usa a cache Add possibilty to use a cache Jun 28, 2022
@aawsome aawsome mentioned this pull request Jul 1, 2022
Closed
@aawsome
Copy link
Copy Markdown
Member Author

aawsome commented Jul 1, 2022

I'l leave the point about removing tree packs open.

This is relevant if you run prune on a repo which is accessed by more than one clients. IMO implementing this needs a rework of internal repository structure. I planned to do this at some point, but I prefer now to work on more features and stability.

There are two workarounds:

  • manually remove all pack files from the cache from time to time (needed ones will be refilled)
  • (when using restic cache dirs) let restic purge unneeded tree packs

=> I open an issue to track this open point

@aawsome aawsome merged commit 6ed332c into main Jul 1, 2022
@aawsome aawsome deleted the add-cache branch July 1, 2022 13:35
This was referenced Jul 1, 2022
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@aawsome