starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 22:26:06 +03:00

[GH-ISSUE #1918] Exclude Specific Folder from Syncing #1283

New issue

Open

opened 2026-02-25 22:39:33 +03:00 by kerem · 7 comments

kerem commented

2026-02-25 22:39:33 +03:00

Owner

Originally created by @FlysonBot on GitHub (Apr 20, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1918

Describe the feature you'd like to request

I want a feature that allow me to exclude specific folder in syncing, so these folder doesn't go to the cloud. This way I can setup another config that sync only that folder to a different service.

Describe the solution you'd like

Same as above.

Describe alternatives you've considered

None.

Originally created by @FlysonBot on GitHub (Apr 20, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1918 ### Describe the feature you'd like to request I want a feature that allow me to exclude specific folder in syncing, so these folder doesn't go to the cloud. This way I can setup another config that sync only that folder to a different service. ### Describe the solution you'd like Same as above. ### Describe alternatives you've considered None.

kerem added the

enhancement

label

2026-02-25 22:39:33 +03:00

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 20, 2025):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

@github-actions[bot] commented on GitHub (Apr 20, 2025): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 21, 2025):

Hey @FlysonBot

thank youf for your feedback! I really appreciate it.

This way I can setup another config that sync only that folder to a different service.

This is already possible with the nested profiles option:

Root folder
- Bookmarks bar - Profile 1
  - bla
  - bar
  - buz - Profile 2 (for this profile set "Allow other profiles to sync this profile's local folder" to disabled)

@marcelklehr commented on GitHub (Apr 21, 2025): Hey @FlysonBot thank youf for your feedback! I really appreciate it. > This way I can setup another config that sync only that folder to a different service. This is already possible with the nested profiles option: - Root folder - Bookmarks bar - Profile 1 - bla - bar - buz - Profile 2 (for this profile set "Allow other profiles to sync this profile's local folder" to disabled)

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@FlysonBot commented on GitHub (Apr 22, 2025):

Ah, I didn't know this is possible! @marcelklehr Thank you very much for letting me know!

Should I close or leave this issue open? I think excluding folder can still be beneficial as some people might just happen to have a folder they don't want to sync for whatever reason.

@FlysonBot commented on GitHub (Apr 22, 2025): Ah, I didn't know this is possible! @marcelklehr Thank you very much for letting me know! Should I close or leave this issue open? I think excluding folder can still be beneficial as some people might just happen to have a folder they don't want to sync for whatever reason.

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 22, 2025):

Yeah, let's leave it open, I've heard other people ask for this as well.

@marcelklehr commented on GitHub (Apr 22, 2025): Yeah, let's leave it open, I've heard other people ask for this as well.

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@servicedevice commented on GitHub (May 16, 2025):

I would like this as well, so that one folder from the bookmarks bar remains off my second device.

@servicedevice commented on GitHub (May 16, 2025): I would like this as well, so that one folder from the bookmarks bar remains off my second device.

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@patienttruth commented on GitHub (Oct 21, 2025):

Thanks for leaving this up so I could find it!

I have a quandary, and I was wondering if one of you could help me wrap my head around it...

Currently I have personal and work profiles in my browser, so each have their own tabs and bookmarks. I've got that all syncing correctly with Floccus. Of note, for the bookmarks I am syncing the / folder in the browser.

Today I tried to create a folder that I would like to sync between my browser profiles. I got that working initially, however when the main bookmark profile (in Floccus) on a secondary browser profile attempted to sync the new folder that was created it threw an error due to the quantity of new bookmarks.

My first thought was "can I ignore that folder in the Floccus profile that syncs the root of that browser profile?", and hence I'm here... I'm not quite wrapping my head around how I'd use the setting that's suggested above, and wonder if it's even necessary in my case. Perhaps I just let both profiles sync the folder? I'm wondering if although it creates duplicates on the server, maybe it doesn't matter?

Any thoughts or caveats?

FYI, writing this out helped my think through it, so I went ahead and let both the shared folder profile, and the main (root) profile of the second browser profile sync by disabling failsafe, and although I know have a duplicate folder on my server, all looks right, and I anticipate this working moving forward.

@patienttruth commented on GitHub (Oct 21, 2025): Thanks for leaving this up so I could find it! I have a quandary, and I was wondering if one of you could help me wrap my head around it... Currently I have personal and work profiles in my browser, so each have their own tabs and bookmarks. I've got that all syncing correctly with Floccus. Of note, for the bookmarks I am syncing the `/` folder in the browser. Today I tried to create a folder that I would like to sync between my browser profiles. I got that working initially, however when the main bookmark profile (in Floccus) on a secondary browser profile attempted to sync the new folder that was created it threw an error due to the quantity of new bookmarks. My first thought was "can I ignore that folder in the Floccus profile that syncs the root of that browser profile?", and hence I'm here... I'm not quite wrapping my head around how I'd use the setting that's suggested above, and wonder if it's even necessary in my case. Perhaps I just let both profiles sync the folder? I'm wondering if although it creates duplicates on the server, maybe it doesn't matter? Any thoughts or caveats? FYI, writing this out helped my think through it, so I went ahead and let both the shared folder profile, and the main (root) profile of the second browser profile sync by disabling failsafe, and although I know have a duplicate folder on my server, all looks right, and I anticipate this working moving forward.

kerem commented

2026-02-25 22:39:33 +03:00

Author

Owner

@marcelklehr commented on GitHub (Oct 26, 2025):

FYI, writing this out helped my think through it, so I went ahead and let both the shared folder profile, and the main (root) profile of the second browser profile sync by disabling failsafe, and although I know have a duplicate folder on my server, all looks right, and I anticipate this working moving forward.

Yeah, the duplicate folder is the only caveat. You can get rid of that using the nested profiles option by disabling syncing of nested profiles in the profile that syncs /, that should prevent the duplicate folder. :)

@marcelklehr commented on GitHub (Oct 26, 2025): > FYI, writing this out helped my think through it, so I went ahead and let both the shared folder profile, and the main (root) profile of the second browser profile sync by disabling failsafe, and although I know have a duplicate folder on my server, all looks right, and I anticipate this working moving forward. Yeah, the duplicate folder is the only caveat. You can get rid of that using the nested profiles option by disabling syncing of nested profiles in the profile that syncs `/`, that should prevent the duplicate folder. :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1283

No description provided.

Rows
Columns