You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Is there a configuration file, or elsewhere, to configure Mountain Duck to only perform a max number syncing (API) events with Box.net on a daily basis? ie. Ability to set a config file rule that says to cache any changes for that day after , say, 500 API requests have been completed on that day.
I have a few programs I use to edit files, e.g. Obsidian, that save files after every new line/CR is put into a text file. This results in Mountain Duck seeing that the file has changed, and then sending up a new version of the file. I.E. A given file gets synced about ~200 times a day. Way more than I need. Really, I only need Mountain Duck to sync the changes maybe 2-3 times a day.
I do see the bandwidth limitation in the UI settings. I set that to ~5mbps. But that still results in the same large number of api requests sent on a daily basis. What I need is to tell it to locally cache changes until the next day, once the number of Box API requests has hit a certain number on a day.
The reason I need this is because there's starting to be a larger monetary charges due to the number of API requests that Mountain Duck has started to make to the Box API via the connected/mounted Box Drive. Again, I'm wanting Mountain Duck to just locally cache file changes if a max number of Box API requests has been made for the day, Then for it to just send up the latest version of the file the following day (not all versions of the file ... just the current saved version of the file) when more API requests are allowed again.
Please advise what can be done to achieve this. Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi. Is there a configuration file, or elsewhere, to configure Mountain Duck to only perform a max number syncing (API) events with Box.net on a daily basis? ie. Ability to set a config file rule that says to cache any changes for that day after , say, 500 API requests have been completed on that day.
I have a few programs I use to edit files, e.g. Obsidian, that save files after every new line/CR is put into a text file. This results in Mountain Duck seeing that the file has changed, and then sending up a new version of the file. I.E. A given file gets synced about ~200 times a day. Way more than I need. Really, I only need Mountain Duck to sync the changes maybe 2-3 times a day.
I do see the bandwidth limitation in the UI settings. I set that to ~5mbps. But that still results in the same large number of api requests sent on a daily basis. What I need is to tell it to locally cache changes until the next day, once the number of Box API requests has hit a certain number on a day.
The reason I need this is because there's starting to be a larger monetary charges due to the number of API requests that Mountain Duck has started to make to the Box API via the connected/mounted Box Drive. Again, I'm wanting Mountain Duck to just locally cache file changes if a max number of Box API requests has been made for the day, Then for it to just send up the latest version of the file the following day (not all versions of the file ... just the current saved version of the file) when more API requests are allowed again.
Please advise what can be done to achieve this. Thanks.
Beta Was this translation helpful? Give feedback.
All reactions