Hello,
i would like to monitor one directory for changes of only 1 file. If this file is changed, it should be uploaded via SFTP to my local Server. I would prefer it, that there is no visualization to the user (i.e dialog, window ore anything else). How can i do this?
What i have done so far: I have started FFS and created a Folderpair (hope thats the correct term). Since there are many files inside of the Source Folder, i have tried to exclude all files, except one. I dont know, if i have done this right, but if i do the check action, it shows only this one file, which i need. After this i setup the Target as FTP, logged in, choosed the correct target folder and choose as Sync Type "Update".
If i run this now in FFS, all works fine. I have now the correct file on the correct target folder. Now i save this as a batch file.
If i have understand this right, i should use RealTimeSync.exe to monitor file changes in future. So i started RealTimeSync.exe and load the batch file from above. But if i click on start, i get a warning, that the target does not support versioning. I didnt want to use Versioning, only a dump copy of the actual file on the target folder. What could id do? Do i have to start RealTimeSync every time, via Startup Folder or as a Service? Or is there any other Way?
Upload Files in Background to SFTP
- Posts: 10
- Joined: 12 Jul 2016
- Posts: 10
- Joined: 12 Jul 2016
Sorry, the error was not about versioning, it is the following error: "The following path does not support directory monitoring". Yes of course, you can not monitor this target. But i didnt want to monitor the target, i want monitor only the source and copy the file to the target, which does not need to be monitored. Where is my failure?
-
- Posts: 2451
- Joined: 22 Aug 2012
It seems you have now defined that both the source- and target-location need to be monitored, like depicted in the top picture of https://freefilesync.org/manual.php?topic=realtimesync.
If your target folder does not need to be monitored or even can not be monitored, simply don't monitor it by deleting/removing the target folder from the RTS watched folder list.
Obviously, RTS should still call the same FFS batch-file upon detection of changes in the source folder.
If your target folder does not need to be monitored or even can not be monitored, simply don't monitor it by deleting/removing the target folder from the RTS watched folder list.
Obviously, RTS should still call the same FFS batch-file upon detection of changes in the source folder.
- Posts: 10
- Joined: 12 Jul 2016
Yeas, indeed. I have both folders like in the Screenshot. If i delete the remote folder, it works.
The second part was about how to start RealTimeSync.exe. Must i start this every time Windows boots again or should i use this as a Service? Or will RealTimeSync.exe started automatically after a Windows Reboot, if i have started the Application only one time? Ahhh and before i forgot it, if i use it as a service, can i disable the little icon in the tray?
The second part was about how to start RealTimeSync.exe. Must i start this every time Windows boots again or should i use this as a Service? Or will RealTimeSync.exe started automatically after a Windows Reboot, if i have started the Application only one time? Ahhh and before i forgot it, if i use it as a service, can i disable the little icon in the tray?
-
- Posts: 2451
- Joined: 22 Aug 2012
In the computer world there are often several ways to skin a cat ...
The way that works for me is to use the (Windows) Task Scheduler to launch
desired applications (e.g. RTS) upon login (=user dependent).
But depending on your use, you might prefer to launch RTS upon startup (=user independent) instead of at login.
Or you take another route (not using RTS) and use the Task Scheduler to directly launch FFS to execute the FFS_batch-file upon logoff or upon shutdown ...
The way that works for me is to use the (Windows) Task Scheduler to launch
desired applications (e.g. RTS) upon login (=user dependent).
But depending on your use, you might prefer to launch RTS upon startup (=user independent) instead of at login.
Or you take another route (not using RTS) and use the Task Scheduler to directly launch FFS to execute the FFS_batch-file upon logoff or upon shutdown ...
