Skip to content

Latest commit

 

History

History
173 lines (117 loc) · 5.84 KB

mupDeploy.md

File metadata and controls

173 lines (117 loc) · 5.84 KB
Raw

Deploy Torrents Duck with Meteor Up

Torrents Duck is a multi users responsive all-in-one seedbox webapp made in Node.js

Warning

This deploy script was made on a Mac with a proper terminal. On Linux this Should Just Work™ but it was not tested on Windows... Send me a feedback if you give it a try 😃

Prerequisites

  • A freshly installed Ubuntu 14 or 16 64bit server with a sudoer user (please not as root) to deploy the seedbox app on it.
    • The user need to be able to sudo without password (this is the only time you might need to ssh into the server).
  • a domain or sub domain pointing to the server.

⚠️ NOTE: All the commands are executed from your PC and not by shh from the server, mup injects the dependencies and the app to the server for you. ⚠️

You must have the following tools installed on your PC (not on the server)

Deployement in 7 steps

1. Get the source code

Open your favorite terminal and go into the directory which you want to store Torrents Duck source code and type the following command. This directory is referenced as path/to/TorrentsDuck later on.

git clone https://github.com/guidouil/TorrentsDuck.git

2. Setting up Meteor Up for your server (this is the hardest part)

Now that you have all dependencies and the source code, we are going to setup Meteor Up to inject the seedbox to your server. Torrents Duck is cutted in 3 containers (duck, torrents and ftp) to be more reliable and use more CPU threads.

Go in source code folder on your local machine and copy your mup deployement scripts with the following commands (Don't be scared your .deploy folder is already mentioned in the .gitignore):

cd path/to/TorrentsDuck
cp .deploy-dist .deploy

Now you have to edit the server informations presents in the .deploy/duck/mup.js, .deploy/torrents/mup.js and .deploy/ftp/mup.js files.

You have to change all iterations of the following words with what is appropriate for your server:

  • MY.SERVER.IP.ADDRESS
  • MY_SERVER_SUDOER_USERNAME
  • MY_SERVER_SUDOER_USERNAME_PASSWORD
  • MY_DOMAIN

You must also change MY.SERVER.IP.ADDRESS in the .deploy/duck/settings.json file and once done copy this settings.json file and past it in the .deploy/torrents/ and .deploy/ftp/ directorys (or apply same modifications to settings.json already present)

If you change a path in the settings.json file, please make sure to change the volumes: in all mup.js files alike.

3. Setting up and deploying the main web app

This is going to install Docker, nginx proxy, MongoDB and other dependencies (also generate ssl)... and yes it is all executed from your PC.

cd path/to/TorrentsDuck
cd .deploy/duck
mup setup
mup deploy

4. Setting up and deploying the bittorent client

This is also the same command to upgrade after you pull updates from git or simply restart the app

cd path/to/TorrentsDuck
cd .deploy/torrents
mup setup
mup deploy

5. Setting up and deploying the FTP server

cd path/to/TorrentsDuck
cd .deploy/ftp
mup setup
mup deploy

Check containers status with mup docker ps

Now the web interface, bittorent and the ftp are ready but we're still can't connect to the FTP.

6. Open the ports for FTP passive mode with iptable

To make FTP accessible from the Internet, we need to translate some ports to the FTP server container. And to do so we need it's IP address. To figure this out we use this commands

cd path/to/TorrentsDuck
cd .deploy/duck
mup ssh
docker exec -it FTP bash
ip addr show

Here you get two network devices status. The localhost and as second devive the eth0. The second line contains the ip of the ftp server. For me it is 172.17.0.7

Now we can translate the port from the serer to the ftp container. Adapt the following commands with the IP you found and also if you changed the ports from settings.json.

cd path/to/TorrentsDuck
cd .deploy/duck
mup ssh
sudo iptables -t nat -A DOCKER -p tcp --dport 9876 -j DNAT --to-destination 172.17.0.7:9876
sudo iptables -t nat -A DOCKER -p tcp --dport 8000:9000 -j DNAT --to-destination 172.17.0.7:8000-9000

You can check the setted iptables rules with this command: sudo iptables -t nat -L -n

If you have some rules you want to remove (previous installs) list nat routes :

sudo iptables -t nat -L --line-numbers

And delet the rules you want with it's line number

sudo iptables -t nat -D DOCKER 2

7. Get admin right

This is not a "bug" : only the first account of the platform gets admin rights (for now). So you need to create the first user using the sign-up from the website we just deployed. Once you have your first account, you need to restart the node application hosted on your server with the following commands :

cd path/to/TorrentsDuck
cd .deploy/duck
mup meteor restart

You are now ready to download at the speed of Node.js and validate new users 😱

Useful mup commands

All mup commands must be run from the .deploy folder of the app from your PC.

// Get system status
mup status
mup docker ps
mup meteor status
mup mongo status
mup nginx status

// If you change anything innside mup.js�, please run:
mup reconfigure
mup deploy

// You can run this as many times as you want it does not reset the datas ;)
mup setup

// and of course
mup help
mup meteor help

Also you might want to refer to Meteor Up documentation

Feedbacks

Please open a issue or submit a PR 😃