guidouil/torrentsduck

A multi users bittorrents client with a responsive web UI that quacks 🦆

Torrents Duck 🦆

A multi users bittorrents clients that quacks

⚠️ Currently in alpha stage ⚠️

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

You need to install Meteor. Follow the instructions.

You also need a local install of MongoDB

you must have two folder writable for your profile from root of hard drive /data/torrents/ and /data/uploads/

Installing and running the main app

Clone or download this repositery and using your terminal in TorrentsDuck/duck folder and install dependencies

meteor npm install

Once done, you can run your local copy with this command of the front end

export MONGO_URL='mongodb://127.0.0.1:27017/TorrentsDuck' && meteor --settings private/settings-dev.json -p 3000

Now go register on http://localhost:3000. First user registered get admin rights but only after a meteor server restart if there is only one user.

Installing and running the bittorrent client app

In another terminal go to the TorrentsDuck/torrents directory and install dependencies

meteor npm install

Once done, you can run your local bittorent client

export MONGO_URL='mongodb://127.0.0.1:27017/TorrentsDuck' && meteor --settings private/settings-dev.json -p 3001

Now you can start torrents transfert from the main interface

Installing and running the FTP server

In another terminal go to the TorrentsDuck/ftp directory and install dependencies

meteor npm install

Once done, you can run your local ftp server

export MONGO_URL='mongodb://127.0.0.1:27017/TorrentsDuck' && meteor --settings private/settings-dev.json -p 3002

Now you can connect by ftp on 127.0.0.1:9876 using the login and password you created on the main web interface

Running the tests

To Be Done™

Deployment

Follow the Meteor Up deployement guide - disponible en Français

Built With

• Meteor - The node.js full stack
• webtorrent - A streaming torrent client for node.js
• ftp-srv - 📮 Modern FTP Server
• Semantic-UI - A UI component framework based around useful principles from natural language.

Authors

• Guillaume Darbonne - Initial work - Guidouil
• Jérémy - French Doc - PixiBixi

See also the list of contributors who participated in this project.

License

This project is licensed under the Apache License - see the LICENSE file for details

Acknowledgments

• You are responsible for what you download using the bittorent protocol

torrentsduck's Issues

mup deploy error

I have followed instructions based on here https://github.com/guidouil/TorrentsDuck/blob/master/_docs/mupDeploy.md

but its seems to failed on mup deploy
mup setup is running just fine

ggrip@GGREAP:~/TorrentsDuck/.deploy/duck$ mup deploy
Building App Bundle Locally

Unable to resolve some modules:

  "@babel/runtime/helpers/interopRequireDefault" in
/home/ggrip/TorrentsDuck/duck/client/lib/semantic-ui/definitions/modules/dimmer.js
(web.browser.legacy)
  "@babel/runtime/helpers/typeof" in
/home/ggrip/TorrentsDuck/duck/client/lib/semantic-ui/definitions/modules/dimmer.js
(web.browser.legacy)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save @babel/runtime


Unable to resolve some modules:

  "diskusage" in /home/ggrip/TorrentsDuck/duck/imports/api/system/methods.js
(os.linux.x86_64)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save diskusage

Errors prevented bundling:
While minifying app stylesheet:
module.js:547:15: Cannot find module 'autoprefixer'
at Function.Module._resolveFilename (module.js:547:15)
at Function.resolve (internal/module.js:18:19)
at Object.require (/tools/isobuild/bundler.js:1927:34)
at packages/minifier-postcss/plugin/minify-css.js:52:37
at Array.forEach (<anonymous>)
at getPostCSSPlugins (packages/minifier-postcss/plugin/minify-css.js:51:43)
at packages/minifier-postcss/plugin/minify-css.js:155:36
at Array.map (<anonymous>)
at mergeCss (packages/minifier-postcss/plugin/minify-css.js:139:23)
at CssToolsMinifier.processFilesForBundle
(packages/minifier-postcss/plugin/minify-css.js:109:18)


While minifying app stylesheet:
module.js:547:15: Cannot find module 'autoprefixer'
at Function.Module._resolveFilename (module.js:547:15)
at Function.resolve (internal/module.js:18:19)
at Object.require (/tools/isobuild/bundler.js:1927:34)
at packages/minifier-postcss/plugin/minify-css.js:52:37
at Array.forEach (<anonymous>)
at getPostCSSPlugins (packages/minifier-postcss/plugin/minify-css.js:51:43)
at packages/minifier-postcss/plugin/minify-css.js:155:36
at Array.map (<anonymous>)
at mergeCss (packages/minifier-postcss/plugin/minify-css.js:139:23)
at CssToolsMinifier.processFilesForBundle
(packages/minifier-postcss/plugin/minify-css.js:109:18)



=> Build Error. Check the logs printed above.

I already run the said fix called

meteor npm install --save @babel/runtime

meteor npm install --save diskusage

but this same error still occur

mup deploy failed

Started TaskList: Pushing Meteor App
[xxx] - Pushing Meteor App Bundle to the Server
[xxx] - Pushing Meteor App Bundle to the Server: SUCCESS
[xxx] - Prepare Bundle
[xxx] x Prepare Bundle: FAILED

npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! network request to https://registry.npmjs.org/node-pre-gyp failed, reason: socket hang up
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

PING registry.npmjs.org (104.16.17.35) 56(84) bytes of data.
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=1 ttl=61 time=1.06 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=2 ttl=61 time=0.848 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=3 ttl=61 time=1.02 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=4 ttl=61 time=0.825 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=5 ttl=61 time=1.03 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=6 ttl=61 time=0.879 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=7 ttl=61 time=1.36 ms
64 bytes from 104.16.17.35 (104.16.17.35): icmp_seq=8 ttl=61 time=1.35 ms

Any suggestions? Thank you

Screenshot?

Is there any?