Getting Started

Treat NNTmux/newznab-tmux as a Laravel application codebase, not a drop-in library. Start by reviewing .env, config/database.php, composer.json, and the release diff for 4.2.
The default DB connection is now MariaDB. For new installs and upgrades, explicitly set DB_CONNECTION=mariadb and verify the host, port, database, user, and collation before running migrations.
Minimal local setup:
- composer install
- npm install && npm run build
- Configure .env with MariaDB credentials
- php artisan key:generate
- php artisan migrate
- php artisan horizon for queue processing
First places to inspect after upgrading:
- The getVideoIDFromSiteID change for zero siteID handling.
- Templates/views migrated to spatie/laravel-html.
- Asset build output after the JavaScript refactor.
First practical use case: run the indexer locally against MariaDB, start Horizon, and validate admin/search pages plus any video/site lookups that pass siteID.

Implementation Patterns

Use MariaDB as the baseline. Keep environment-specific DB settings in .env and avoid relying on implicit MySQL defaults.
Use Horizon for queue visibility and operations. Run it under Supervisor in production and check php artisan horizon:status plus failed jobs during upgrades.
Use Laravel Scout for search indexing. Configure the Scout driver per environment and rebuild/import indexes after major data or dependency changes.
In Blade/templates, use spatie/laravel-html where the codebase has migrated. Keep new form/input generation consistent with that package rather than mixing multiple HTML-building styles unnecessarily.
After pulling 4.2, rebuild frontend assets with the project’s npm scripts. Avoid editing compiled assets directly; work from the source JS and rebuild.
For the getVideoIDFromSiteID fix, treat 0/missing site IDs as a valid “no result” path. Add or update tests around zero, null, and invalid IDs before relying on the method in imports or admin workflows.
Extend behavior through Laravel’s normal seams: Artisan commands, jobs, events/listeners, service classes, and Blade components. Keep custom indexer logic outside vendor code so Composer updates remain safe.

The MariaDB default is the most likely upgrade pitfall. Existing deployments that relied on MySQL defaults may need explicit DB_CONNECTION=mariadb, connection tuning, and checks around collations, full-text indexes, JSON columns, and migration compatibility.
The zero-siteID fix suggests callers previously could hit unexpected behavior. Audit call sites and guard before querying or processing when siteID is 0, empty, or absent.
The spatie/laravel-html migration can introduce escaping or markup differences. Clear view caches after deploying, compare rendered forms/inputs, and avoid double-escaping values passed through helper methods.
The JavaScript refactor may require a clean asset build. Run npm ci where possible, rebuild, clear Laravel caches, and verify browser-cached assets are not serving stale files.
Dependency bumps include PHPUnit 12.5, Horizon 5.35, Scout 10.19, Symfony HTTP Client 7.3, and Rector updates. Confirm the runtime PHP version and CI matrix match PHPUnit/Horizon requirements before upgrading production.
Debug upgrades in this order: php artisan about, DB connectivity, migrations, Horizon worker health, failed jobs, Scout index status, compiled view/assets, then application logs.
For production upgrades, back up the database, deploy with maintenance mode if schema changes are involved, run migrations, rebuild caches/assets, restart Horizon, and smoke-test search plus admin workflows.