What is the best torrent client for Ubuntu

Recently I wanted to do some research on data which is available only via torrent. Also it is a very huge file. I don't want to do this in my local machine, so I decided to spin up a Digital Ocean droplet. After some search, I found that Deluge is a best tool to do it. Deluge provides both GUI and console support. In this article, we will see how to install and use deluge from the console.

Install Deluge in Ubuntu

sudo add-apt-repository ppa:deluge-team/ppa
sudo apt-get update
sudo apt-get install deluge deluged deluge-console


How to run

1. Run Deluge daemon


This will run deluge in the background.

2. Run Deluge Console


This will open up new console where you can type deluge commands.

3. Add a torrent file to start download

In order to download, you need to add your torrent file to deluge using:

add -p torrent_path torrent_file_name



add -p /home/john songs.torrent

Other useful commands

You can use following commands in the deluge console.

info        - Show information about the torrents
add         - Add a torrent
rm          - Remove a torrent
cache       - Show information about the disk cache
exit        - Exit from the client.
halt        - Shutdown the deluge server.
pause       - Pause a torrent
resume      - Resume a torrent
help        - displays help on other commands

Here info is very useful command which displays current stats of the torrent download.

Hope it helps. Have a great day.

View comments

Sending Logstash Logs to Loggly

We are using Logstash for our log management. We integrated logstash with ElasticSearch, and Kibana UI. However it does not work very well to us. So we were looking for possible tools to visualize the logs without much work. Finally, we decided to use Loggly. Then we just follow the steps provided by loggly in their documentation. Unfortunately it does not work for Logstash version 1.5. After spending few hours, we made it work. Here are the steps.

Install Loggly Plugin

Since Logstash version 1.5, there is a new plugin management system. To install a Logstash Loggly plugin, use the following command:

sudo bin/plugin install logstash-output-loggly

Create Logstash configuration

Create a logstash-loggly.conf file with following contents

      key => "TOKEN"
      host => "logs-01.loggly.com"
      proto => "https"

where TOKEN - your customer token from the source setup page

You can place this file under /etc/logstash/conf.d/.

Restart the Logstash

Restart Logstash to send the files to Loggly.

service logstash restart

It may take a few minutes to index the event. If it doesn’t work, you can see /var/log/logstash/logstash.err.

View comments

Working with upcoming posts in Jekyll

We used to work on more than one post at a time and publish them in future. So you just want to test them while writing the blog, but you don't want publish them to your live blog immediately. There are 3 different ways to achieve this in jekyll.

1. With published settings

You can include a line in your post meta data to indicate whether a post is published or not:

published: true


published: false

Set published to false if you don’t want a post to show up when the site is generated.

To preview your site locally, you can --unpublished option

jekyll server --unpublished

When you want to make the post to live, just remove the published flag or set it to true.

2. With future dated posts

You can write your blogs with future dated. There is a setting which does something similar - show future dated posts.

To preview your site locally, you can --future option

jekyll server --future

Make sure that you have following setting in your _config.yml file. This will hide future dated posts from your live blog.

future: false

3. With drafts folder

As you know, Drats are the posts you’re still working on and don’t want to publish yet. To get up and running with drafts, create a _drafts folder in your site’s root. You can place your posts inside the drafts folder.

- _drafts/
  - my-draft-post.md

To preview your site locally, you can --drafts option

jekyll server --drafts

Make sure that you have following setting in your _config.yml file. This will hide drafts posts from your live blog.

show_drafts: false

When you want to publish the post to live blog, move your post from _drafts to _posts folder.

I recommend drafts folder for upcoming posts. Because it is much cleaner and easy to maintain when you work with team. If you have any other tips, share it on comments.

View comments