How we use BitTorrent to improve our design sharing workflow
1–10 of 27 posts
Re: How we use BitTorrent to improve our design sharing workflow
#2Congrats on using bitorrent for syncing files. You need at least RAID1 setup to don't lose information. Never use only one hdd.
Re: How we use BitTorrent to improve our design sharing workflow
#3I was hoping this was going to be something where the files themselves were distributed so that they didn't take up space on everyone's machines, a la MogileFS[1], but alas.
This is always a point of pain for us: in our studios we work from a central file server, so our shiny iMacs with their 1TB drives all have about 90% capacity on them — but we don't have any easy way to pool all that extra capacity and use it even as overflow for our central fileserver.
The search continues...
Re: How we use BitTorrent to improve our design sharing workflow
#4IMHO btSync is a great ideia but the use of random ports makes hard to use in some setups.
Re: How we use BitTorrent to improve our design sharing workflow
#5Note that the author seems to misunderstand a few things about BitTorrent sync:
1. Firstly, Btsync is not open-source (unfortunately), as he claims. [1]
2. 24-hour secrets don't give someone read access for 24 hours. They must be redeemed within 24 hours after creation, but if they are redeemed on time they become permanent read-only secrets.
[1] - Answered in these threads: http://forum.bittorrent.com/topic/8816-will-syncapp-be-open-... http://forum.bittorrent.com/topic/17782-bittorrent-sync-faq-...
Re: How we use BitTorrent to improve our design sharing workflow
#6I was hoping this was going to be something where the files themselves were distributed so that they didn't take up space on everyone's machines, a la MogileFS[1], but alas. This is always a point of pain for us: in our studios we work from a central file server, so our shiny iMacs with their 1TB drives all have about 90% capacity on them — but we don't have any easy way to pool all that extra capacity and use it eve…
That's what git-annex is for. Everyone has a list of all the files, and then if you want to access one, you can just do "git annex get [file]" and it'll get it from any of the machines that happen to have that file. If you want to delete it, "git annex drop [file]" will ensure at least N machines keep a copy of the file before deleting it.
I use it to manage files between my VPS, desktop, laptop and NAS, with each machine having a different subset of the whole pool, and it works great.
Re: How we use BitTorrent to improve our design sharing workflow
#7How does this handle a situation where multiple designers edit large files at roughly the same time?
Re: How we use BitTorrent to improve our design sharing workflow
#8IMHO btSync is a great ideia but the use of random ports makes hard to use in some setups.
You can set the port in the configuration:
http://labs.bittorrent.com/experiments/sync/get-started.html...
The closed source nature of Bitorrent Sync is biggest drawback IMHO. But I guess FOSS clones are on their way. The bit torrent protocol in itself is very well known after all.
Re: How we use BitTorrent to improve our design sharing workflow
#9Note that the author seems to misunderstand a few things about BitTorrent sync: 1. Firstly, Btsync is not open-source (unfortunately), as he claims. [1] 2. 24-hour secrets don't give someone read access for 24 hours. They must be redeemed within 24 hours after creation, but if they are redeemed on time they become permanent read-only secrets. [1] - Answered in these threads: http://forum.bittorrent.com/topic/8816-wil…
I'm curious why this is being downvoted. Is the information incorrect?
Re: How we use BitTorrent to improve our design sharing workflow
#10Note that the author seems to misunderstand a few things about BitTorrent sync: 1. Firstly, Btsync is not open-source (unfortunately), as he claims. [1] 2. 24-hour secrets don't give someone read access for 24 hours. They must be redeemed within 24 hours after creation, but if they are redeemed on time they become permanent read-only secrets. [1] - Answered in these threads: http://forum.bittorrent.com/topic/8816-wil…
Ah my bad – I've corrected the open source claim and I'll reword about the 24 hr secrets. Thanks.