nweeks

Enabling Api On A Non-Config-File Setup

Recommended Posts

Hi all,

 

I've got a HEAP of folders syncing beautifully between many machine, and I'd like to add API functionality to one machine for monitoring / automated adding of folders.

 

By the looks of it, I need to:

 

do a `btsync --dump-sample-config`

 

manually re-add all 438 shared folders in the JSON structure,

Add the storage location to switch on the API.

 

This isn't really going to work.

 

is there any way I can run a `btsync --dump-running-config` instead?

 

Please say yes. Pleeeeease...

 

(Or, is there a way of adding the required flag to the '.sync/settings.dat' ?)

 

Nige.

Share this post


Link to post
Share on other sites

You don't need to dump a sample config, just start Sync with a very basic config file.

 

For example, on Windows, to enable to API, simply create a config file with the following:

{   "storage_path" : "/Users/username/AppData/Roaming/BitTorrent Sync",   "use_gui" : true,   "webui" : {        "listen" : "0.0.0.0:8888",        "login" : "username",        "password" : "password",        "api_key" : "your_api_key"    }}

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.