As our site got bigger, trying to run everything on 1 server proved too much for it to handle so we needed to move some of the services onto different servers but still all work as a team.

Our main server runs on Ubuntu and uses Apache2 but for serving static files and for serving lots of simultaneous connections Nginx is more lightweight and suited to the job, that is why we have 2 extra servers, 1 for Images and 1 dedicated to the API, we are also using a base Debian install for these servers.

If you want to follow these steps on an Ubuntu machine simply type “sudo su” at the command line.

Get everything up to date

nano /etc/apt/sources.list

Add to the bottom:

deb http://packages.dotdeb.org stable all

wget http://www.dotdeb.org/dotdeb.gpg
cat dotdeb.gpg | apt-key add -
rm dotdeb.gpg
apt-get update
apt-get upgrade

Add www to skel

adding www to skel will mean when a new user is added the www folder will be added to their home directory, we will use this for storing the data (on our debian installs /home has the majority of the disk space, so it makes sense to store the data there)

mkdir /etc/skel/www

Add a user

In our case the user we are adding is called fanart, change this to whatever you want, but just be aware to change it in all the places it’s used inthe rest of the guide

adduser fanart

Install MySQL

apt-get install mysql-server mysql-client

Install Nginx

apt-get install nginx

Install PHP

apt-get install php5 php5-fpm php-pear php5-common php-apc php5-mcrypt php5-mysql php5-cli php5-gd php5-curl php5-imagick php5-mcrypt php5-memcache

Set up the vhost

In our case the vhost is assets.fanart.tv change this to whatever you are going to be using

cp /etc/nginx/sites-available/default /etc/nginx/sites-available/assets.fanart.tv

The default file has a lot of crap in it so you might want to clean up your vhost first by removing all the commented out lines, you still have default if you need to reference anything, then either add the following (or uncomment if it’s in the file)

nano /etc/nginx/sites-available/assets.fanart.tv

Change the index line so it has index.php in it first

index index.php index.html index.htm;

location ~ \.php$ {
   fastcgi_split_path_info ^(.+\.php)(/.+)$;
   fastcgi_pass 127.0.0.1:9000;
   fastcgi_index index.php;
   include fastcgi_params;
}

At this point the site is onlu available, we need to set it to enabled, to do this we create a symlink:

ln -s /etc/nginx/sites-available/assets.fanart.tv /etc/nginx/sites-enabled/assets.fanart.tv

Install phpMyAdmin

phpMyAdmin makes it a bit easier to set up things, so install it

apt-get install phpmyadmin

You will see the following questions:

Web server to reconfigure automatically:
don’t select anything, just tab to the OK as neither are installed

Then it will ask
Configure database for phpmyadmin with dbconfig-common?

Select No

You can now find phpMyAdmin in the /usr/share/phpmyadmin/ directory. Now we must configure our vhost so that nginx can find phpMyAdmin in that directory.

nano /etc/nginx/sites-available/assets.fanart.tv

Then add the following before the last }

location /phpmyadmin {
root /usr/share/;
index index.php index.html index.htm;
location ~ ^/phpmyadmin/(.+\.php)$ {
try_files $uri =404;
root /usr/share/;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include /etc/nginx/fastcgi_params;
}
location ~* ^/phpmyadmin/(.+\.(jpg|jpeg|gif|css|png|js|ico|html|xml|txt))$ {
root /usr/share/;
}

}
location /phpMyAdmin {
rewrite ^/* /phpmyadmin last;
}

Also add any other rewrites you need, on our api server we added

location /webservice/newmovies {
root /home/www/;
rewrite ^/webservice/newmovies/(.*)/(.*)/$ /webservice/newmovies.php?key=$1&date=$2 last;
rewrite ^/webservice/newmovies/(.*)/$ /webservice/newmovies.php?key=$1 last;
}

location /webservice/newtv {
root /home/www/;
rewrite ^/webservice/newtv/(.*)/(.*)/$ /webservice/newtv.php?key=$1&date=$2 last;
rewrite ^/webservice/newtv/(.*)/$ /webservice/newtv.php?key=$1 last;
}

location /webservice/ {
root /home/www/;
rewrite ^/webservice/(.*)/(.*)/(.*)/(.*)/(.*)/(.*)/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2&id=$3&format=$4&type=$5&sort=$6&limit=$7&update=1 last;
rewrite ^/webservice/(.*)/(.*)/(.*)/(.*)/(.*)/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2&id=$3&format=$4&type=$5&sort=$6&limit=$7 last;
rewrite ^/webservice/(.*)/(.*)/(.*)/(.*)/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2&id=$3&format=$4&type=$5&sort=$6 last;
rewrite ^/webservice/(.*)/(.*)/(.*)/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2&id=$3&format=$4&type=$5 last;
rewrite ^/webservice/(.*)/(.*)/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2&id=$3&format=$4 last;
rewrite ^/webservice/(.*)/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2&id=$3 last;
rewrite ^/webservice/(.*)/(.*)/ /webservice/newapi.php?section=$1&key=$2 last;
rewrite ^/webservice/(.*)/ /webservice/newapi.php?section=$1 last;
}

Performance tuning

The following made a MASSIVE difference to the cpu load on the API server, each php5-fpm process went from using 20-40 %CPU to between 4-12 (and usually around 4-6), so if you are seeing high load in php5-fpm processes have a try with the following settings, bare in mind though, the server has 16GB or RAM, so you may need to adjust the settings.

first you need to edit the APC config:

nano /etc/php5/conf.d/apc.ini

In my case it just had extension=apc.so, in any case if the following directives dont exist in the file add them to the bottom else change them.

apc.shm_size=512
apc.shm_segments=2

This changes the shm_size from the default 32M to 512M, so guides I found said to use M but that resulted in php5-fpm refusing to reload for me, and checking the php documentation it states this should be an integer expressing the size in MB.

then start nginx

service nginx start
service php5-fpm reload

With the late Steve Jobs so publicly against a smaller slate it may have been a surprise to some people when Apple announced the iPad Mini, but the success of the Nexus 7 and Amazons 7inch tablets probably left them with little choice but to take the fight to Google and Amazon by announcing the iPad Mini.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Build

iPad Mini: Apple have always been at the forefront on the quality angle, and this latest product is no different, made from an aluminium and glass design, the iPad Mini exudes quality.  Weighing in at just 308g and 7.2mm thin should make it comfortable to use for extended periods of time.

Nexus 7: Android has always been the budget cousin to apple when it comes to quality, there are hundreds of cheap android devices out there and this has hurt androids image as a quality product in the mind of a lot of consumers.  Having said that, the Nexus 7 manufactured by Asus is a very nice product, sporting a comfortable dimpled rubberized removeable back and glass covering the entire front the Nexus 7 is a real step up from its cheap sibling.  At  340g and 10.5mm thin its not as thin and light as the iPad Mini, but is still lighter than than most of its rivals and is should be just as comfortable to use for long periods as the iPad Mini.

Kindle Fire HD: The Kindle Fire HD is the first of Amazons tablets to come to the UK, but it’s a good looking device is a little wider than you would expect thanks to having a consistent 2cm bezel all the way around. At 395g and 8.8mm thin it sits between the other two tablets in thinness but is heavier than both.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Screen

iPad Mini: Apple products have always used fantastic screen, this one is a 7.9inch LED Multi-Touch IPS display, which ensures wide viewing angles.  The screen is a bit disappointing in that it doesn’t feature a Retina display, but no doubt we will see that in the iPad Mini 2, or iPad Mini S.  The screen has a 1024×768 resolution which equates to a 163ppi, which means it’s the same screen quality as the iPad 2.

Nexus 7: The screen on the Nexus 7 is fantastic, and while it might not be in the same category as a full fat iPad with a Retina display, its running at 1280×800 resolution with 216ppi meaning it easily beats the 1024×600 of most 7inch rivals and the iPad Mini.  The Scratch-resistant Corning® Fit Glass should also add a bit of protection to the screen.

Kindle Fire HD: The screen on the Kindle is comparable to that in the Nexus 7 with an IPS screen running at the same resolution and PPI.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Camera

iPad Mini: A 5-megapixel rear facing camera and a front facing FaceTime HD camera have been fitted to the iPad Mini.

Nexus 7: Personally, I believe rear facing cameras on a tablet are pointless and only serve to point the user out as a wally and/or showoff, especially when most peoples phone will have a camera as good as or better than that of the tablet, as well as easier to hold and use.  Google obviously came to a similar decision and opted for a 1.2megapixel front facing camera only, which should cover you for any Skype and Google+ needs.

Kindle Fire HD: Amazon have also gone with a front facing only 1.3megapixel HD camera primarily for use with Skype.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Operating System

iPad Mini: iOS is undeniably a great operating system, slick, intuitive and well designed, the iPad Mini is set to get the iOS 6 treatment which promises a tweaked user interface with a new look App Store and iCloud support.

Nexus 7: Android has always been a bit of a mixed bag due to supporting so many different devices, however the Nexus 7 ships with Android Jelly Bean 4.1 out of the box with a 4.2 update forthcoming, and it really helps the Nexus 7 shine with notable features including speedier performance thanks to Project Butter, a smarter keyboard, a more sophisticated voice search, the new Google Now service, and 4.2 will also bring the ability to have multiple user accounts.

Kindle Fire HD: The kindle has a modified version of Android 4.0.3 Ice Cream Sandwich, however the tablet is so tied into Amazons App Store that you are locked out of using any other App Stores including Google Play and if you are thinking of installing a competing app for reading e-books in ePub format (which the Kindle doesn’t support itself), forget it.

iPad Mini vs Nexus 7 vs Kindle Fire HD – App Store

iPad Mini: Apples App store is without doubt the best, it has the largest collection of apps designed specifically for tablets and the strict vetting procedure means the apps are generally of high quality and consistant.

Nexus 7: Googles play store is slowly catching up and a lot of the best apps from Apples App Store have been ported over, the ability to add 3rd party App Stores such as Amazons is also a huge bonus.

Kindle Fire HD: The Amazon App Store is pretty good, and has a lot of the popular apps from the Play store, however, none of googles apps are on it, and if you want apps from the Amazon store, you can install the Amazon marketplace on the Nexus 7.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Power

iPad Mini: The same dual core A5 that is used in the iPad 2 and iPhone 4S is used in the iPad Mini which should ensure everything runs nice and snappy.  While it’s not the A6X from the 4th Gen iPad it should be more than capable for its intended use.

Nexus 7: The Nexus 7 is packing some serious power, with a quad core Tegra 3 processor to tackle multitasking and deliver smooth performace while the 12 core GPU should be able to handle even the most demanding mobile games.  The additional 5th battery saving core takes care of everyday tasks which should help preserve battery life.

Kindle Fire HD: The kindle is running on a 1.2Ghz OMAP processor which while a capable processor doesn’t feel as snappy as the iPad or Nexus 7.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Connectivity

iPad Mini: According to Apple the dual band 802.11n Wi-Fi delivers twice the performance of previous iPad models, with LTE compatibility in addition to standard 3G support means it’s ready for 4G, assuming you buy a device with these included of course, because as with all iPads there are multiple different versions to choose from, each with a hike on the price front.  The iPad Mini also includes Bluetooth 4.0.

Nexus 7: With a 3G version forthcoming, the Nexus 7 also has some interesting connectivity options including Bluetooth, NFC and GPS.  The GPS in particular allows you to use the device as a sat nav and I installed co-pilot with good results.

Kindle Fire HD: The kindle has dual-band, dual-antenna Wi-Fi which uses MIMO (Multiple In, Multiple Out) to improve speed and reliability.  It also has Bluetooth and a HDMI out port, but lacks both NFC and GPS.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Battery

iPad Mini: The iPad mini should make it through the day with Apple promising 10 hours of battery life.

Nexus 7: Google claims that the nexus 7 will deliver 9 hours if you are consuming content such as HD video and extends that to around 10 hours for more everyday tasks.

Kindle Fire HD: The kindle performs well on battery life, in most battery tests The iPad mini comes out slightly ahead, and the Nexus 7 slightly behind, making the kindle a good middle ground.

iPad Mini vs Nexus 7 vs Kindle Fire HD – Price

iPad Mini: Starting off with a price point of £269 will get you the 16GB Wi-Fi only model, with the 32GB coming in at £349 and the 64GB at £429, if you want 3G connectivity you are going to need to add £100 at each price point.

Nexus 7: The big selling point of the Nexus 7 is it’s price, while the 16GB iPad Mini will set you back £269 the equivalent Nexus 7 costs just £159, with the 32GB costing £199 (vs £349) and the 32GB + 3G finishing up the lineup costing £239 (vs £449).

Kindle Fire HD: Like the Nexus 7 the kindle Fire HD is aggressively priced with the 16GB option costing £159 with ads (£169 without ads) and the 32GB option costing £199 with ads (£209 without ads).

iPad Mini vs Nexus 7 vs Kindle Fire HD – Conclusion

It’s hard to pick a clear winner, and it will mostly come down to your personal circumstances, if you have other Apple products and are therefore tied to the Apple ecosystem the iPad mini may be the best option for you.  On the other hand The Nexus 7 is considerably cheaper for a product that is comparable and in some cases superior, and is probably the product I’d go for on a cost conscious decision, even over the Kindle as the locked down nature of the Kindle makes it frustrating, true you could root the kindle, but most people just want something that will work out the box.

Do you have any thoughts on this matter?  Let me know in the comments.

Paid memberships pro is a great plugin from http://www.paidmembershipspro.com/ it allows you to create paid membership levels and while its basic form may be a bit limited, and I must stress the word bit, as out the box it’s pretty flexible, it makes extensive use of filters making it very easy for 3rd parties to customise it.

First thing to do is create a folder in your plugins directory called pmprocustom then create a file called pmpro-customisations.php the names of the folder and file aren’t important.

Add the following to the file:

<?php 
/* Plugin Name: PMPro Customizations 
Plugin URI: http://www.lockstockmods.net 
Description: Customizations for Paid Memberships Pro 
Version: 0.1 
Author: Kode 
Author URI: http://fanart.tv */ 

function my_pmpro_profile_start_date($startdate, $order) { 
  $next_year = strtotime(" + 1 Year"); 
  $startdate = date("Y", $next_year) . "-01-01T0:0:0"; 
  return $startdate; 
} 
add_filter("pmpro_profile_start_date", "my_pmpro_profile_start_date", 10, 2); 

function my_pmpro_checkout_level($pmpro_level) { 
  $current = date("n"); 
  $persplit = $pmpro_level->initial_payment/6; 
  switch($current) { 
    case "3": case "4": $pmpro_level->initial_payment = $persplit*5; break; 
    case "5": case "6": $pmpro_level->initial_payment = $persplit*4; break; 
    case "7": case "8": $pmpro_level->initial_payment = $persplit*3; break; 
    case "9": case "10": $pmpro_level->initial_payment = $persplit*2; break; 
    case "11": case "12": $pmpro_level->initial_payment = $persplit; break; 
  } 
  return $pmpro_level; 
} 
add_filter("pmpro_checkout_level", "my_pmpro_checkout_level", 10, 1); 

When a members checkout out a particular membership level it will check the month and set the initial payment amount as a pro rata proportion, in my case I have it set to 2 month increments, therefore if the initial payment was £40 and the recurring amount was also £40

• Jan/Feb joiners would pay the full amount
• Mar/Apr joiners first payment would be £33.33, therafter £40
• May/Jun joiners first payment would be £26.67, therafter £40
• Jul/Aug joiners first payment would be £20.00, therafter £40
• Sep/Oct joiners first payment would be £13.33, therafter £40
• Nov/Dec joiners first payment would be £6.67, therafter £40

If you wanted to change it, it is very easy, say you wanted to do the splits in 4 month increments, you would change the code to

function my_pmpro_checkout_level($pmpro_level) { 
  $current = date("n"); 
  $persplit = $pmpro_level->initial_payment/3; 
  switch($current) { 
    case "5": case "6": case "7": case "8": $pmpro_level->initial_payment = $persplit*2; break; 
    case "9": case "10": case "11": case "12": $pmpro_level->initial_payment = $persplit; break; 
  } 
  return $pmpro_level; 
} 

Another alternative would be on a monthly basis

function my_pmpro_checkout_level($pmpro_level) { 
  $current = date("n"); 
  $persplit = $pmpro_level->initial_payment/12; 
  $pmpro_level->initial_payment = $persplit*(12-$current); 
  return $pmpro_level; 
} 

Hope this helps someone

The site hosts a collection of images for all your favourite media and grows daily due to having some great contributors.

At the time of writing the site hosts over 50,000 images, with the music section currently being the biggest section on the site, but the Movie section is new to the site and really starting to increase.

Every image submitted to the site goes through a quality control process, so you can be sure that most images you get from the site will be top quality (there are a few images that slipped through the nets, but they are few and far between), and if the site is missing images you would like it’s very easy to make requests.

The site has a pretty comprehensive set of API’s to allow 3rd parties access to the data for use in things like scrapers, to use the API’s you will need an API key and links to documentation for the API’s can be found in the side bar of the same page.

Music Artwork

The artist section is currently the biggest section on the site and has over 30,000 images.  The site has a range of different image types including wallpapers (also known as backdrops, backgrounds or fanart) that are all 1080p, ClearLOGOs (a transparent image with the artists logo on it), cdART (a transparent cd disc), and album covers.

There is a template for cdART: Photoshop template / GIMP template and several tutorials on how to use them Photoshop video tutorial / GIMP tutorial / Photoshop tutorial

Top 5 artists/bands with the most artwork

1. The Rolling Stones (152 Images)
2. Motörhead (136 Images)
3. The Beatles (85 Images)
4. Nightwish (84 Images)
5. Iron Maiden (83 Images)

TV Artwork

Like the Music section the TV section has many different types of image types that can be used for a variety of different applications.

Top 5 TV Shows with the most artwork

1. Dexter (72)
2. Doctor Who (68)
3. Fringe (55)
4. The Simpsons (51)
5. Breaking Bad (50)

Movie Artwork

Movie artwork is the newest category and so is currently the smallest, however it’s growing at a pretty fast rate.

Top 5 Movies with the most artwork

1. Star Trek (29)
2. WALL-E (20)
3. Alice in Wonderland (19)
4. Avatar (19)
5. TRON: Legacy (18)

If you would like to contribute, please let me know

Changelog

2010-06-21 – Initial publication, includes DVD Cover banners templates
2010-06-21 – Added Wide banner templates
2010-06-21 – Added link to get ClearART Logos

All Downloads

Series banners

To be completed

Season banners

DVD Cover style

Season Banners must 400 x 578 pixels, and in a jpg format.  To save the PSD as a jpg go to file/Save for Web.

Preview:

Download:

Wide style

Season banners must be 758 x 140 pixels.

Preview:

Download:

Image resources

To get logos and for other artwork resources check out fanart.tv

I recently took the plunge and built my first unRAID server, it’s been running for a month now and i’ve been really happy with it. This tutorial will attempt to help you set up SABnzbd+ and Sickbeard on your unRAID server and get you one step closer to using unRAID to consolidate the machines you need running.

This wouldn’t have been possible without the great guys on the unRAID community forum, particularly Romir who created the AIO and Dependencies package.

I have included for download the All In One package as well, but for the purpose of this guide i am using the dependencies package as it should allow you to upgrade your SABnzbd installation.

This guide assumes you have a cache drive, however, both AIO or dependencies setup should work without a cache drive, just change the paths.

Using a cache drive or manually mounted disk is a good idea because sickbeard does a lot of debugging at the moment and will hit the flash a lot if stored on there, also you don’t want downloads downloading onto the flash.

Alternatively instead of a cache drive or manually mounting another drive you could put everything onto the array, somthing like replacing /mnt/cache/.custom with /mnt/disk1/custom would probably work or you could create a user share.

If you can’t get the files from their official sources you can get them here:
Note: There is a file embedded within this post, please visit this post to download the file.

Change log

2010-06-03 – Published initial draft
2010-06-03 – Added loop in go script to allow /mnt/cache to mount
2010-06-03 – Added instructions for updating sickbeard
2010-06-03 – Added images/links to sickbeard, SABnzbd and unRAID
2010-06-03 – Added screenshots
2010-06-07 – Added automatic updater written by beckstown with modifications by mlrtime3 and me (Kode)
2010-06-07 – Changed paths to use wildcards for sickbeard
2010-06-07 – Added source for sickbeard-updater.sh for those who don’t want to download it just want to paste it into nano

Set up

Log into your unRAID server and type the following commands

cd /mnt/cache
mkdir .custom
cd .custom
wget http://sourceforge.net/projects/sabnzbdplus/files/sabnzbdplus/sabnzbd-0.5.2/SABnzbd-0.5.2-src.tar.gz/download
wget http://github.com/midgetspy/Sick-Beard/tarball/master
ls

Your filenames might be different, just replace the filenames below with the filesnames you have

tar zxf SABnzbd-0.5.2-src.tar.gz
tar zxf midgetspy-Sick-Beard*.tar.gz
rm SABnzbd-0.5.2-src.tar.gz
rm midgetspy-Sick-Beard*.tar.gz
mv midgetspy-Sick-Beard-* sickbeard
mv SABnzbd-0.5.2 sabnzbd
cd /boot/custom
wget http://www.bibliognome.com/unraid/SABnzbdDependencies-1.3-i486-unRAID.tgz

edit your go script and add the following, replacing 192.168.1.6 with whatever ip it runs on

# determine if cache drive online, retry upto 7 times
for i in 0 1 2 3 4 5 6 7
do
    if [ ! -d /mnt/cache ]
    then
      sleep 10
    fi
done

# If Cache drive is online, start SABNzbd
if [ -d /mnt/cache ]; then
  # Start SABnzbd and sickbeard
  installpkg /boot/custom/SABnzbdDependencies-1.3-i486-unRAID.tgz
  python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d -s 192.168.1.6:88
  nohup python /mnt/cache/.custom/sickbeard/SickBeard.py &
fi

The for loop will pause installing SABnzbd and sickbeard for up to 70 seconds if the cache drive isn’t mounted yet, then, as suggested by Joe L. there is an if statement so if it goes over 70 seconds it wont try to install SABnzbd and sickbeard if the cache drive still isn’t mounted.

SABnzbd+ 0.5.2

You should be able to hit SABnzbd on http://tower:88/wizard if that doesnt work try typing python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d -s 192.168.1.6:88 at the commandline

Complete the SABnzbd setup wizard

Go to Config/Folders

Change Completed Download Folder: to /mnt/cache this will mean that when the mover script runs it will move the completed download off the cache drive and into the appropriate locaton. This wont affect TV downloads though because we will set up sickbeard to post process them.
change Post-Processing Scripts Folder: to /mnt/cache/.custom/sickbeard/autoProcessTV then click save changes.

Go to config/categories

Select sabToSickBeard.py from the script dropdown in the TV row

Sickbeard

Sickbeard should be accessable from http://tower:8081
In the unRAID terminal type

mv /mnt/cache/.custom/sickbeard/autoProcessTV/autoProcessTV.cfg.sample /mnt/cache/.custom/sickbeard/autoProcessTV/autoProcessTV.cfg

If you don’t chang the port, username (blank) or password (blank) in config/General you don’t need to edit this file.
Go to Config/General

In the defaults section select your preffered quality and tick Use Season Folders, click save changes

Go to Config/Episode Downloads

In the NZB/Torrent section, select SABnzbd as the NZB Action
In the SABnzbd section enter your SABnzbd settings (the api key can be retrieved by going to SABnzbd and going to /config/general)
Save changes

Go to Config/Search Providers

Enter the details for your search provider

Updating sickbeard with a script

Install

cd /mnt/cache/.custom
wget http://www.lockstockmods.net/dloads/sickbeard-updater.sh
chmod +x sickbeard-updater.sh

Run

Any time you want to update sickbeard just run the following

sh /mnt/cache/.custom/sickbeard-updater.sh

your old sickbeard folder is backed up to sickbeard_backup. If the update fails, do NOT just rerun it as you may lose your settings.

Updating sickbeard Manually

As we are using a development snapshot version of sickbeard you are going to want to keep it up to date, this is easy to do, but its a manual process.

cd /mnt/cache/.custom
wget http://github.com/midgetspy/Sick-Beard/tarball/master
tar zxf midgetspy-Sick-Beard*.tar.gz
rm midgetspy-Sick-Beard*.tar.gz
mv sickbeard/sickbeard.db midgetspy-Sick-Beard-*/
mv sickbeard/config.ini midgetspy-Sick-Beard-*/
mv sickbeard/autoProcessTV/autoProcessTV.cfg midgetspy-Sick-Beard-*/autoProcessTV/
rm -rf sickbeard
mv midgetspy-Sick-Beard-* sickbeard

Extras

sickbeard-updater.sh

Find below the source for the sickbeard-updater.sh

#!/bin/sh

# Required setting: Absolute path to parent directory of sickbeard folder.
path=/mnt/cache/.custom
sb="sickbeard"

# Optional setting to switch branch. DONT CHANGE IF YOU DONT KNOW WHAT THAT MEANS!
branch=master

# Get webgui access settings from autoProcessTV (needs to be set up) and shutdown sickbeard.
host=`echo | grep 'host=' $path/${sb}/autoProcessTV/autoProcessTV.cfg | cut -d '=' -f2 | tr -d '\r'`
port=`echo | grep 'port=' $path/${sb}/autoProcessTV/autoProcessTV.cfg | cut -d '=' -f2 | tr -d '\r'`
user=`echo | grep 'username=' $path/${sb}/autoProcessTV/autoProcessTV.cfg | cut -d '=' -f2 | tr -d '\r'`
pass=`echo | grep 'password=' $path/${sb}/autoProcessTV/autoProcessTV.cfg | cut -d '=' -f2 | tr -d '\r'`
wget --user=$user --password=$pass http://$host:$port/home/shutdown
sleep 5s

# Get source and untar it.
cd $path
wget http://github.com/midgetspy/Sick-Beard/tarball/$branch
tar zxf midgetspy-Sick-Beard*
rm midgetspy-Sick-Beard*.tar.gz

# Make backup copy of old ${sb} & setup new ${sb} version
cp -R ${sb} ${sb}_backup
mv ${sb}/sickbeard.db midgetspy-Sick-Beard-*/
mv ${sb}/config.ini midgetspy-Sick-Beard-*/
mv ${sb}/autoProcessTV/autoProcessTV.cfg midgetspy-Sick-Beard-*/autoProcessTV/
rm -rf ${sb}
mv midgetspy-Sick-Beard-* ${sb}

# Start SickBeard as daemon
cd ${sb}
nohup python SickBeard.py &