SickRage is dead, long live SickRage!

There’s a new and more stable fork of SickRage available! Are you ready to switch?

What happened?

I don’t know the details, but according to Reddit a guy named echel0n originally forked SickRage from SickBeard for various reasons including adding TvRage support. A team of talented developers helped him to improve the software, but after a while echel0n suddenly left. Some time later echel0n returned to the project and thought he could be a little dictator and managed to piss off the rest of the team which resulted in they starting their own branch.

How does this affect me?

Since most of the developers moved from SickRageTV to SickRage you can expect SickRage to get all the upcoming cool features. I’m not even sure if  SickRageTV is going to get fixed at this point as it’s currently broken and unusable. I’ve already made the switch to the new repository and it’s actually a whole lot better already, both in terms of performance and stability.

How do I switch to the new branch on Synology or XPenology?

SickRageBackupFirst of all make sure that you have a backup of your configuration. Login to Sickrage, navigate to “Backup and Restore”, create a backup and store it in a safe location. Take a look at my previous post if you are unable to access the web interface. You can also backup the necessary files manually by downloading them using SCP.

The files you should backup are:

cache/
cache.db
config.ini
failed.db
sickbeard.db

SickRage InstallThe next step depends on which package you are using. Since the SickRage package has been discontinued by SynoCommunity, I recommend to uninstall it and use the “SickBeard Custom” package from now on. If you are already using the “SickBeard Custom” package you can either re-install and restore your backup (recommended) or try a manual upgrade.

Once you’ve uninstalled the package, install “SickBeard Custom” and specify the following when prompted:

Fork URL: git://github.com/SickRage/SickRage.git
Fork branch: master

The package will automatically download the latest version using git and you should be able to restore your configuration from the backup without any issues. Before restoring, you might want to verify that git_remote_url is set to the correct repository and web_port is set to the correct port in config.ini. I’m not sure if the restore process uses that property or ignores it, but it’s a good thing to be aware of it so it doesn’t point to the wrong repository after doing a restore.

How to I switch branch manually?

It’s also possible to switch branch directly using git. First of all make sure that you backup the following files either through the web interface or by downloading them using SCP from the SickRage directory:

cache/
cache.db
config.ini
failed.db
sickbeard.db

Now it’s time to stop SickRage. The command may differ depending on your setup. If you are on Synology or XPenology you may stop the package from the “Package Center” in DSM:

/etc/init.d/sickrage stop

Next navigate to the SickRage directory and execute the following commands in sequence. If you are on Synology/Xpenoloy you’ll need to specify the full path to git such as /volume1/@appstore/git/bin/git.

git remote set-url origin https://github.com/SickRage/SickRage.git
git fetch origin
git reset --hard origin/master

Now simply start SickRage again and it should work without any issues. Remember to update config.ini so git_remote_url points to the new repository if nessesary.

 

Share this:

9 comments, add yours.

Avatar

Giovanny

Thanks for your post, very helpful, just one thing, when I import my old backup settings, it change the port so with sickBeard custom I have the custom port, but after import settings it changed to the sickRage port 8899.

Hope this helps someone, beacuase It was driving me crazy, when the page didn’t load.

Benjamin Krause

Benjamin Krause

Author

Thanks! I totally forgot mentioning the port number. Appreciate your comment! 🙂

Avatar

lexton

Good article! That echel0n dude seems a nut case if you ask me.
He’s telling users that they get viruses and stuff if they change to the new fork. Like WFT.? And he broke sickrage completely in 2 months time, that in itself is accomplishment… No fixes, no word, forum not working etc. How can you put any trust in that.?

Anyway i have also switched to the new fork, and thank god stuff is working like it should.!

Avatar

Daniel

Perfect, thank you. Exactly what I was looking for! 🙂

Nice and precise guide as well.

Avatar

Bru

Hi! thanks for your help,

What can I do if I do not have a actual instalation of sickrage and I can’t copy thos file to restore later?

Regards.

Benjamin Krause

Benjamin Krause

Author

Your welcome! 🙂

Benjamin Krause

Benjamin Krause

Author

Thank you!

Benjamin Krause

Benjamin Krause

Author

I’m not sure if I understand your question… If you don’t have SickRage installed it’s just to download the SickBeard-custom package and specify the correct fork URL.

Avatar

Martin

Many thanks, this saved my ass, been having so much trouble with SickrageTV for a couple of months!

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.