Thus said Martin Vahi on Tue, 16 May 2017 22:43:07 +0300: > Are there any "heart-beat" options available, wher a cron job might > call something like
No, however, there are options to control how much Fossil will sync in a single round-trip. Fossil does synchronize individual artifacts in batches and all artifacts that are sent/received in a single round-trip are committed (in the RDBMS sense of the word) to the repository, so if your connection drops, or your hosting provider limits process time, you don't have to resynchronize those parts that were already successfully synchronized. Some of the settings that control how much data is sent in a round-trip (or how much time is permitted) are: max-download (server) max-download-time (server) max-upload (client) You can get to the server settings using the /setup_access page on your server. You can get to the client settings from the command line (or using fossil ui on your workstation). Of course, if the size of your artifacts is greater than these settings it may not help as much. From the output that you sent, it looks like maybe your artifacts are quite large so you won't be able to take advantage of these settings: > mishoidla/sandbox_of_the_Fossil_repository$ fossil push --private > Push to https://martin_v...@www.softf1.com/cgi-bin/tree1/ > technology/flaws/silktorrent.bash/ > Round-trips: 1 Artifacts sent: 0 received: 0 > server did not reply > Push done, sent: 651648435 received: 12838 ip: 185.7.252.74 Andy -- TAI64 timestamp: 40000000591b78f8 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
