gregcaulder
-
Posts
10 -
Joined
-
Last visited
-
Days Won
1
Posts posted by gregcaulder
-
-
Since the windows version allows for the developer API, it would be so beneficial to be able to have a Web GUI for a windows version of BTSync. Having to RDC in every time to add a sync, or remove, or check on the status is such a pain.
-
-
Dantounet,
Could you please elaborate which issue do you have on 1.3.80? Bad share ID or bad message len?
I still have the bad ShareID (STATE_BEGIN) error message, and I am not sure why. I am running on 1.3.87 on Windows.
-
gregcaulder/koldkat - please see this thread.
Thanks for not actually answering the question. The link you provided still does not provide the answer. Let me rephrase the question to help you better understand I guess.
Why is the limit set to 50? would make sense that it would be an advanced parameter that i can be allowed to change it.
What were the realistic reason for setting it to 50?
-
#!/usr/bin/python# SHA1 encoderimport hashlibimport osfrom base64 import b32encodesecret_to_generate = raw_input('Please Enter the name to encode for the secret: ')hash_object = hashlib.sha1(secret_to_generate)hex_dig = hash_object.hexdigest()base32_dig = b32encode(hex_dig)print 'This is the HEX Digest: ', hex_digprint 'This is your secret to share: ', base32_digNote: I find this useful as I created many folders and only display the printed list on the web. From the folder name, I already know a key, so I just create the new secret remotely, assign it to my folder, and I can download whatever I need from home.
Any possible way of getting this in the form of a PHP script.
I tried wrapping my head around it, but i cant get RO keys to match from RW keys.
-
Yes, this can be done - you'll need to setup a separate Sync folder for each client on your "central server", and assign each one a read-only secret (with the corresponding full-access secrets given to each client respectively)
This will allow each client to sync (backup) to a dedicated folder on your "central server", but any changes made on the central server itself won't propagate back to clients, and client's will not communicate with each other as long as they each have separate secrets.
However, you don't mention just how many "clients" you propose to have connecting to your "central server" at any one time? If it's more than 50, Sync running on your central server won't be able to establish connections to them all simultaneously.
Why wont sync be able to establish connection to more than 50 "clients" at one time?
-
All a webgui for a windows install.
I would perfer to manage the BTSync running on a windows system from a webgui, so i don't have to go the the actual system, or remote into it.
G
-
Ability to make the request url be able to be SSL.
For example (listed in API documentation):
http://[address]:[port]/api?method=get_folders[&secret=(secret)]
Allow for HTTPS
https://[address]:[port]/api?method=get_folders[&secret=(secret)]
-
So I figured before I start my ventures in writing some scripts for Sync, I'd create a nice and easy way to access the API from PHP. It has all the current API functions included. It requires a Sync install with the API enabled.
Link : iGARET/BTSync-PHP
Docs: http://igaret.github.io/BTSync-PHP/classes/BTSync.html
Let me know if you have any questions/suggestions!
You didn't add in anything for the ability to pass a username and password.
I added it on my own and got it to work.
How Are People Using Sync 1.4?
in Sync General Discussion
Posted
I agree, installed it on one system, and will not update it on any of my other systems.