Simply nZEDb

Set up your own nZEDb usenet indexer in no time at all. This is a docker based installation based on the super-slim alpine linux distro.

Requirements

• Linux (64-bit x86 based distro - Debian, Ubuntu, whatever) or macOS 10+
• docker 1.11+
• git
• make
• python 2.7
• virtualenv

Installation

Step 1 - Command line setup

ProTip: Setup docker to run without having to use sudo unless you like typing in your password again and again.

$ git clone https://github.com/slydetector/simply-nzedb.git nzedb
$ cd nzedb

# Create a python virtualenv for docker-compose
$ make venv

# Create a copy of the *single* config file
$ cp etc/simply_nzedb.conf.example etc/simply_nzedb.conf

# Update config file with usenet, irc, socks, etc settings
$ vim etc/simply_nzedb.conf

# Setup the ./data dir which contains nzedb config, nzbs, mysql data, log files, etc
$ bin/setup_data_dir

# Build the image(s) - Optional, but recommended for latest version.
$ [sudo] make build 

# Start up nzedb to do initial setup
$ [sudo] make start 

Step 2 - Automated web setup

# This will run through the web setup for you using settings from simply_nzedb.conf.
# Logs are in web_setup.log
$ bin/web_setup

Step 3 - Sane defaults

# Update settings db table with locations of various executables like ffmpeg, mediainfo, etc
# and subscribe to alt.binaries.teevee for verification
$ [sudo] bin/apply_defaults

# Restart to pick up changes
$ [sudo] make start

Step 4 - Verification

# Attach to tmux and verify things are working by
# next'ing through the windows.
#
# Cheat sheet for getting around in tmux:
#
# Key         Action
# --------------------------------------
# Ctrl-a n    Next window
# Ctrl-a c    Create new window
# Ctrl-a d    Detach from tmux
# 
$ [sudo] make attach

Go to http://<hostname>:8800/browse?t=5000 and you should see some TV releases soon.

Congratulations, you've just accomplished the hardest part of running nZEDb, setting it up!

Commands

Run make to see what else you can do.

$ make 
Welcome to simply-nzedb!

Core commands:

  attach - attach to nzedb's tmux session
  backup - backup database. nzedb must be running
  help - print this help
  logs - print container logs
  mysql - mysql client
  mysqltuner - run mysql tuner
  pull - pull the latest version
  restore - restore last database backup. nzedb must be running
  shell - shell into the nzedb container
  start - start nzedb (restarts if it is already running)
  status - shows running containers
  stop - stops nzedb

Developer commands:

  build - build docker images locally instead of downloading from docker hub
  test - run acceptance tests

Upgrading to a newer version of nZEDb

See UPGRADE.md for version specific upgrade instructions.

• Run make backup or you'll probably regret things if things go horribly wrong
• Run git pull to update to the latest docker files
• Run make pull to pull the latest docker images
• Run make start to restart nZEDb. The database schema is updated if necessary when starting up.

If after an upgrade, make attach fails, it is usually an indication that the database is getting updated or running migration steps. Use make logs | less -R to check on the progress and try again in a few minutes.

Customizing MySQL

You can customize mysql by modifying the etc/nzedb.cnf file. For example:

[mysqld]
key_buffer_size = 2G
innodb_buffer_pool_size = 8G
group_concat_max_len = 32768
innodb_file_per_table = 1

Be warned, you can do more harm than good by randomly uncommenting lines and increasing values. Regardless of how beefy your server might be, many of those values are closely related to other values in that list, and by increasing them you run the risk of saturating your connection pool and/or starving your server of necessary resources.

You are strongly encouraged to read the MariaDB documentation before adjusting the cnf file: https://mariadb.com/kb/en/library/configuring-mariadb-with-mycnf/ https://mariadb.com/kb/en/library/server-system-variables/

Prepopulating the database with API keys, settings, etc

You can customize mysql settings by creating data/etc_mysql_conf.d/nzedb.cnf. e.g.

# Create a copy of the private.sql.example file
$ cp etc/private.sql.example etc/private.sql

# Update the private.sql file with your API keys, backfill settings, and anything else.
$ vim etc/private.sql

Most of the settings in etc/private.sql are defaults, so although it does not hurt to keep them in you can delete any lines you don't need. Once you've got your installation set up and running the way you like it, open up the settings and tmux tables in adminer and copy the values you've changed into your private.sql file. If you ever need to spin up a docker instance on a new machine all your values will be prepopulated.

Accessing Adminer and/or phpMyAdmin

You can access the Adminer database manager via <your nzedb ip address/url>:8880. If installed, phpMyAdmin would be at <your nzedb ip address/url>:9800.

Docker networking works slightly different than traditional networking. When accessing Adminer (or phpMyAdmin or other addons), the host is database, not localhost. The database is nzedb and the user is either root or nzedb.

TODO

• PreDB auto-population

Acknowledgements

• Based on work from alp-nzedb
• Hats off to the guys moving nZEDb forward.

Help!

Try the Gitter chat room