Looking for souls willing to test v3.

[jprochazka]

I am working on wrapping up testing for v3. This includes a bunch of bash script refactoring as well as the rewrite including major modernization changes to the portal. The portal is a total rewrite of the previous portal, in fact not much remains of the v2.x portal in this upcoming release. I have been over the changes locally and I am now looking for feedback from the community. Please note there are reworked backup and restore scripts in the ~/bash/tools directory. You may want to treat these as beta quality as well being I am the only one testing so far on limited hardware.

You can Install this branch from the repo root with ./install.sh --branch portal. The installer fetches and switches to the selected branch before it runs the portal setup. If you are already on the portal branch, just run ./install.sh --development normally. It should be fully capable of retaining your current data.

Look for screenshots of the new portal being posted here shortly. I meant to release some along with this announcement but a few bugs encountered after upgrading Angular caused me to run out of time this evening. I promise though as opposed to the old version with its static pages and archaic MRTG style graphs you will not be let down. That is unless I missed any big bugs along the way...

Speaking of bugs feel free to post them in the issue tracker. I will be keeping an eye out for any reports.

Anyways here is all that has changed since the old portal.

Note: The following does not cover refactoring of bash scripts.

ADS-B Portal Rewrite: Beta Test Announcement

Release Status

This release is Alpha/Beta quality (pre-release). Expect rough edges and treat it as test software, not a production-stability release.

The feature set is now locked. From this point forward, development is focused on bug fixes, reliability, and stabilization only.

Screenshots are incoming and will be added in a follow-up update.

What Changed

The portal has been migrated from the legacy PHP/lighttpd stack to a new architecture:

• Flask backend
• Angular frontend
• Nginx + Gunicorn deployment
• Full REST API with Swagger/OpenAPI docs at /api/docs/

Major Capabilities

• Multi-user auth with roles (Admin/User) and JWT login
• Unified live aircraft view with dump1090 + dump978 data
• Flight history, search, positions, comments, and purge tools
• UAT (dump978) history endpoints
• ACARS APIs and management
• Interactive graph data APIs (RRD-backed minus the collectd requirment)
• Admin panels for users, links, blog, devices, settings, and scheduler
• Built-in background jobs (collection, maintenance, scheduler visibility)

Tester Checklist

• Install and run the portal end-to-end on a clean supported system or well backed up existing one
• Verify login, token refresh, and role-based access
• Validate live map data, flight history, UAT data, ACARS, and graphs
• Check scheduler jobs are running and visible in admin
• Test settings updates and persistence across restarts
• Confirm Nginx and backend service restart behavior after changes
• Validate API behavior and docs at /api/docs/
• Confirm legacy import path behavior if upgrading from older portal data
• Report regressions, crashes, data-loss risks, and API contract mismatches

Backup and Restore Testing

Backup and restore tooling exists for both legacy and new portal versions and needs active testing.

Legacy v2 (PHP/lighttpd):

• Docs: bash/tools/PORTAL_BACKUP_RESTORE_V2.md
• Scripts:
  • bash/tools/portal_backup_v2.sh
  • bash/tools/portal_restore_v2.sh

Current v3 (Flask/Angular):

• Docs: bash/tools/PORTAL_BACKUP_RESTORE_V3.md
• Scripts:
  • bash/tools/portal_backup_v3.sh
  • bash/tools/portal_restore_v3.sh

Please test both backup and restore workflows applicable to your deployment, including restore validation after service restart.

Platform Requirement

Full portal install requires a 64-bit OS.

32-bit Raspberry Pi OS (armhf) is not supported for the full portal install path.

Issue Reporting

Please report issues with enough detail to reproduce quickly:

• Hardware model and CPU architecture
• OS version and whether it is 64-bit or 32-bit
• Fresh install vs upgrade/migration scenario
• Exact steps to reproduce
• Expected behavior vs actual behavior
• Relevant logs (installer output, service logs, API errors)
• Database type in use (sqlite, mysql, or postgresql)
• Whether backup/restore or legacy import was involved

Focus reports on defects and stability risks. Since feature scope is locked, feedback is most useful when tied to reproducible bugs, regressions, or operational failures.