Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make desktop client check external storage #4462

Closed
AndyXheli opened this issue Apr 27, 2022 · 5 comments
Closed

Make desktop client check external storage #4462

AndyXheli opened this issue Apr 27, 2022 · 5 comments

Comments

@AndyXheli
Copy link

AndyXheli commented Apr 27, 2022

Currently if a file is added to an exteral storage not via Nextcloud the desktop client will not detect there's a change. You have to go under Nextcloud web and open the folder and then it will updated the external folder and then the desktop client will sync it down. Is there a way to make the desktop client request for an update on the external folders. I think this would be awesome and I'm sure alot of people would like the same thing.

https://help.nextcloud.com/t/external-storage-not-updating/61879/3
https://help.nextcloud.com/t/smb-share-external-storage-support-not-syncing-to-client/93551
nextcloud/server#1564
nextcloud/server#10413

image
Since the sever only has an option for updated once every direct access can you make the desktop client request for the change making the server access the folder ?

@sm8ps
Copy link

sm8ps commented Aug 20, 2022

I strongly support this and would like to ask for what reasons this is not the standard behavior. From a user perspective it does not make sense having external storage shown in the web-interface but changes not reflecting in their local files. One expects the two to simply agree when using a sync client. Maybe there are cases where it is not desirable or possible but IMHO it should be at least optional to have the client sync with the server state also for external storage.

I have been struggling with this issue for years until I finally realized that this seems to be expected behavior for the current state of the sync client. Please make it behave more as expected from a user's perspective.

@johnnyq
Copy link

johnnyq commented Nov 9, 2022

  • I have this problem too
  • I have a printer/copier that sends the scans to an FTP Server (Its the only option it allows)
  • I created an external share in nextcloud called scans that connects to the FTP Server
  • I set the check for changes once every direct access
  • Everyone uses the Desktop Sync Client so this option does not work
  • My hacked up solution was create a seperate nextcloud user called scan_user
  • setup the external storage on that user and share the external storage with everyone
  • Create Cron script that runs every minute to check for file updates only for the scan_user so this cuts down on scanning everyones files each time.

* * * * * root docker exec -t nextcloud-aio-nextcloud php occ files:scan scan_user

This is obviously a very hacked solution but it does work

@FesTGig
Copy link

FesTGig commented Dec 3, 2022

same issue here.
we run NC on a productive server and have big problems with people not having the lates files from the external storage. I would call this not only an enhancement, for us it is more a bug! Any chance that will get a fix?

@sm8ps
Copy link

sm8ps commented Dec 3, 2022

I could finally resolve the problem by using the files_inotify app which needed some additional tweaking, cf. icewind1991/files_inotify#23.

@swartzlib7
Copy link

swartzlib7 commented Nov 21, 2023

Hi y'all,

thank you for this here. I had no idea this could happen, but I think it will not happen for my setup.

See my last comment on this issue here today for a possible workaround that might suite you (or not) while you wait on the official fix.

#6099

Sincerely,
Stephen

@AndyXheli AndyXheli closed this as not planned Won't fix, can't repro, duplicate, stale Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants