I’m not sure that I understand correctly, but you won’t be able to add files on the server directly. You always have to go through the web interface. If for some reason your workflow requires this, you should use either curl to upload the files into the server (safest method) or set up a cron job that scans for the new files like so:
occ files:scan --all
But this will break functionality of apps that uses post upload file hooks, like for example anti virus or search providers as they don’t know about the file.
Two choices to solve this, one would be to use the desktop client to bring the files from the file server into ownCloud and then bring them back to your desktop. The second one is available inside our Enterprise version, we do have listening to events on the Windows File Server … please contact us for a try out.
For small setups the file:scan solution layed our by Erik, will suffice, indeed.
Can you make sure that after the file deletion the scan occ command ran? It won’t work before this runs.
Which version of owncloud server are you using? To figure this out you could go to:
Uploading directly to the ownCloud’s data folder is NOT SUPPORTED
files:scan is intended to be used to fix several potential problems. It is NOT INTENDED to be used continously.
If you want to upload files, go through the ownCloud’s webDAV interface. You can also upload files directly to the storage backend by using the ownCloud’s external storage support
maybe you can give more details on the “does not work”? Looks to me that this is lacking information like e.g. the current behavior and the expected behavior.
When I run the command occ file: scan --all, the command does not generate an error, but the files on my file server do not synchronize with my Windows client.
As a reminder, on my owncloud server, I created a mount to back up the files directly to a file server (NAS).