Cache is eating up my boot volume #18135
Unanswered
anonemusic
asked this question in
Q&A
Replies: 0 comments
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.
-
Hi, just purchased Mountain Duck.
I manage an NPO website (WordPress) with 27GB of content uploaded by multiple contributors. Due to financial reasons, we don't have a staging site. I decided to create a local sandbox on my Mac M4. Local.app will host a copy of the live site so I can check WP Core/Plugin updates, as well as other backend testing on function.php.
ChronoSync supports only SFTP, while our ISP supports only FTP. This is why I got Mountain Duck. In my scenario, I will never need to have Mountain Duck upload to our ISP. It only needs to be current, syncing from the live site to my local. I need to update the ISP manually.
To avoid any caching taking up my boot volume, I pointed both the Mount Location and the Cache Location to one of the attached RAID5 drives. The mode is left to the default, "Integrated."
For some reason, the Cache Location keeps reverting to
~/Library/Group\ Containers/G69SCX94XU.duck/Library/Application\ Support/duck/Cache
I also found many large files with 'mountainduck' string on my boot volume. Not sure what I am doing wrong. Any help would be appreciated. Thank you in advance.
-Hiro
Beta Was this translation helpful? Give feedback.
All reactions