Repository navigation
Version 8.0
Make sure to backup your config and your database before updating to Version 8.0.
A rebuild, not an update
- The listening page and the administration page are new programs. Neither is built on Angular: each is written with the browser's own components, with no framework runtime in the page, and the Angular client is gone from the project. Nothing was translated line by line — the new screens were laid out against the version 6.6.3 pages so they open where you left them. The guides name the handful of things that deliberately differ: the Scanner webapp guide for listening, and chapter 8 of the administrator guide for the administration screens.
Updating from version 6.6.3
- Your existing database is carried into the new one by itself. The first time Version 8.0 opens a version 6.6.3 database it runs the upgrade, names each table it found in the log, and finishes before it serves anything to anyone. It rewrites your database where it sits and removes the old tables once it has finished, so back the database up before you start it. Nothing the upgrade cannot carry is thrown away: a row with no place in the new structure is kept in a
migrationArchivetable together with the reason it could not be carried, and chapter 24 of the administrator guide walks the whole path and shows what was kept. Everyone who was signed in to the administration interface is signed out, so expect to log in again.
The listening page
- It is built to be used with a keyboard and a screen reader, where the older page was built for a mouse. What you have selected is always visible, a skip link jumps past the navigation, announcements reach a screen reader as they happen, and every control — the player, the call list, the menus, the dialogs — can be reached without a mouse.
The log and the administration page
- The log now names which part of the server wrote each line — the directory watchers, the downstreams, logins, the live feed, retention, and the rest — and the console and the service log carry that name in front of every line. The log view filters on it: pick a part of the server, search the message text, see how many lines each part wrote as clickable counts, and turn auto-refresh on or off. Chapter 14 of the administrator guide carries the parts, the filters, and where to look when something is wrong.
- The administration page asks before it uses a newer version, the way the listening page already does. When it finds a version newer than the page you have open, it opens a question titled
New version available.Nokeeps the page you have open and the question comes again next time; onlyYesreloads the page and starts the new version. Nothing is ever reloaded by itself, and answeringNoleaves unsaved edits where you left them. Chapter 8 of the administrator guide carries the question and both answers, and chapter 25 says why a page opened over a plain address on another host never asks.
Getting audio in
- The audio converter that ships inside each release now reads the audio out of whichever file format and coding your recorder wrote, and always writes the same output: AAC in an m4a file at 32 kbit/s. When it cannot read a recording's audio, the recording is stored exactly as it arrived and the log says why, in the converter's own words rather than only the version of the program that ran. Chapter 13 of the administrator guide explains the four conversion modes.
One licence for the whole server
-
The server no longer holds its real-time interface apart from the rest of itself. The whole server — the REST API and the live listener connection alike — is GNU GPL version 3, and a deployment you host yourself answers both for its own clients without an agreement with anyone. The separate policy document earlier versions pointed at is gone; chapter 27 of the administrator guide states the licence.
-
Numerous fixes and improvements across the server, the administration, and the listener's web application.