When Teleport updates a project it downloads every file every time, instead of only downloading new or changed files; what am I doing wrong?
Each time you run a project, Teleport first gets any new files that were pending from a previous session. Next, it checks to see that all of the old files are up-to-date (during this phase, the status bar will say ‘Updating’). When Teleport updates files, it queries the server, and asks whether that file has changed since the last time Teleport retrieved it. If it hasn’t, Teleport doesn’t do anything. If it has, Teleport immediately downloads the new file and saves it (overwriting the old file) in the project folder. The update check is very efficient — if the file hasn’t changed, Teleport doesn’t do anything. However, a file may still sometimes get completely reloaded on update, even if it hasn’t changed, for one of two reasons– (1) The remote server isn’t reporting the modification date for the file. In this case, Teleport cannot know what to do, and re-loads the file. (2) The document is generated dynamically by the server, and even though its content may remain identical, its dat
Related Questions
- When Teleport updates a project it downloads every file every time, instead of only downloading new or changed files; what am I doing wrong?
- I changed a Descriptor (such as: Project "ACB" to "ABC"). How do I change all the Time Records with the old Descriptor value?
- Does File Scrub record in the logs when system date and time are changed?
