A Usenet Indexer
- dev-dev / 1.x-dev
This package is auto-updated.
Last update: 2021-05-07 10:21:12 UTC
NNTmux automatically scans usenet, similar to the way google search bots scan the internet. It does this by collecting usenet headers and temporarily storing them in a database until they can be collated into posts/releases. It provides a web-based front-end providing search, browse, and programmable (API) functionality.
NNTmux improves upon the original design, implementing several new features including:
- Optional multi-threaded processing (header retrieval, release creation, post-processing etc)
- Advanced search features (name, subject, category, post-date etc)
- Intelligent local caching of metadata
- Optional sharing of comments with other NNTmux and newznab sites
- Optional tmux (terminal session multiplexing) engine that provides thread, database and performance monitoring
- Image and video samples
- SABnzbd/NZBGet integration (web, API and pause/resume)
- CouchPotato integration (web and API)
System Administration know-how. NNTmux is not plug-n-play software. Installation and operation requires a moderate amount of administration experience. NNTmux is designed and developed with GNU/Linux operating systems. Certain features are not available on other platforms. A competent Windows administrator should be able to run NNTmux on a Windows OS.
4GB RAM, 2 cores(threads) and 20GB disk space minimum.
If you wish to use more than 5 threads a quad core CPU is beneficial.
The overall speed of NNTmux is largely governed by performance of the database. As many of the database tables should be held within system RAM as possible. See Database Section below.
PHP 7.2+ (and various modules) MySQL 5.6+ (Postgres is not supported)
The installation guides have more detailed software requirements.
Most (if not all) distributions ship MySQL with a default configuration that will perform well on a Raspberry Pi. If you wish to store more that 500K releases, these default settings will quickly lead to poor performance. Expect this.
As a general rule of thumb the database will need a minimum of 1-2G buffer RAM for every million releases you intend to store. That RAM should be assigned to this parameter:
Use mysqltuner.pl for recommendations for these and other important tuner parameters. Also refer to the nZEDb project's wiki page: https://github.com/nZEDb/nZEDb/wiki/Database-tuning. This is particularly important before you start any large imports or backfills.
Follow NNTmux Ubuntu install guide:
For composer install and getting NNTmux follow this guide:
Run the docker init command
Copy .env.example -> .env, configure .env, mandatory fields:
- APP_KEY=base64:wbvPP9pBOwifnwu84BeKAVzmwM4TLvcVFowLcPAi6nA= # or generate one!!!
Copy docker-compose.override.yml.dist to docker-compose.override.yml and remove any services that you don't want to run locally. Make any other adjustments to suit your needs.
Copy over localized configuration from docker/php-overrides.ini to docker/php-overrides.local.ini and any other adjustments you'd like to make.
Copy your composer's auth.json file (can probably be found in ~/.composer/auth.json) to docker/composer-auth.json.
Run the installation script
docker-compose run --rm web docker/install.sh
For routing, you can use a proxy container like nginx-proxy. The default configuration is to route the indexer to nntmux.local. You'll also need to add the following to your
Now, you can start the web container:
docker-compose up -d web # Tail the logs starting with the most recent 15 lines. Look for errors and resolve any issues. docker-compose logs --tail=15 --follow web
Open http://nntmux.local and sign in as the admin user with the credentials configured in the .env file. Configure site and tmux settings.
Start the tmux container:
docker-compose up -d tmux # Attach to tmux ./cli/docker tmux-attach
There are other commands available in cli/docker (i.e. to stop the tmux session -- you should do this before stopping the tmux container!).
Support is given on irc.synirc.net #tmux channel.
NNTmux is GPL v3. See LICENSE.txt for the full license.
Other licenses by various software used by NNTmux:
Net_NNTP => W3C
Zip file creation class => No license specified.
simple_html_dom.php => MIT
All external libraries will have their full licenses in their respectful folders.