[Feature Request] Ignore specific folders for Cloud Sync
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Hi there,
I asked about this on Libretro forums and r/RetroArch, and the answer is that right now, this feature doesn't exist.
===
The cloud sync feature works great on my side, and is ideal for most cores and their associated saves files, or even system for some.
However, the current implementation shows some clear limits when it comes to permissions and upload size control.
A very basic example:
Dolphin’s (Gamecube / Wii) save folder includes Wii nand, but also a lot of other stuff, especially - custom texture packs.
I have maybe 5 texture packs installed for games like Metroid Prime, MadWorld, Super Mario Sunshine etc.
These packs takes around 40gb of free space, and are located in Retroarch/saves/dolphin-emu/user/load.
So, right now, if I setup cloud sync to the save folder, these texture packs will be cloud synced and eat up all allocated free space on any free service available. I don't even mention how long it takes to upload these, of course.
Now, I don't know how Webdav works, but a very basic solution used by many programs consists about adding an empty .txt file (example: nocloud.txt) in a folder you do not want to be synced / scrapped.
Would it be difficult to implement something like that ? I don't think a user friendly solution exists to manually add all the folders you want to be ignored using GUI, but maybe retroarch.cfg ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Start by locating RetroArch's cloud sync implementation and its configuration handling, then determine how folder exclusions could be represented. Done should mean a user can mark or configure specific folders so they are omitted from synchronization, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100