Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CLOSED] Cache / storage #110

Closed
feross opened this issue Sep 21, 2014 · 3 comments
Closed

[CLOSED] Cache / storage #110

feross opened this issue Sep 21, 2014 · 3 comments

Comments

@feross
Copy link
Member

@feross feross commented Sep 21, 2014

Issue by iamale
Saturday May 17, 2014 at 16:12 GMT
Originally opened as https://github.com/feross/bittorrent-client/issues/14


This one might be considered either a feature request or a question.

Is there any way to store downloaded files somewhere and seed them back?

@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

Comment by fisch0920
Saturday May 17, 2014 at 20:53 GMT


Kind of :)

bittorrent-client needs to run in the browser, so it can't store the files to the filesystem. The webtorrent executable, however, is meant to be run out of the browser, so it's the correct place to put storage to filesystem logic. The latest non-merged version in the webtorrent repo has this working.

@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

Comment by feross
Monday May 19, 2014 at 02:25 GMT


Yep, Travis is right. You need to use the webtorrent package if you want the file to be automatically saved to disk.

$ npm install webtorrent -g
$ webtorrent --help

If you use bittorrent-client directly, it will still automatically do seeding for you, but you will need to write the code to save the file to disk.

@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

Comment by iamale
Monday May 19, 2014 at 15:06 GMT


👍 Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.