update documentation to remove bionic

.github/ISSUE_TEMPLATE/bug_report.md

@@ -26,7 +26,7 @@ Version from the upgrade popup if you can reach it.
 **Installation method:**
 
 - OS: [e.g. Ubuntu]
-- OS Version [e.g. 16.04.5 LTS (Xenial Xerus)]
+- OS Version [e.g. 18.04.5 LTS (Bionic Beaver)]
 - Method: [e.g. `./install` script or packages]
 - Details: [how did you call the install script, where did you get packages from]
 

docs/_docs/install.md

@@ -10,9 +10,9 @@ permalink: /install
 ## Minimum System Requirements
 
 - One of the following Linux distributions
-  - Ubuntu 16.04 LTS, 18.04 LTS
+  - Ubuntu 18.04 LTS
   - Debian 10
-  - Raspberry Pi OS 9, 10 (formerly Raspbian)
+  - Raspberry Pi OS 10 (formerly Raspbian)
 - 1 Ghz Processor
 - 2 GB RAM recommended (1 GB required)
 - Wired internet connection and static IP address for on-prem install

docs/_docs/upgrading.md

@@ -26,28 +26,25 @@ requirements as per semver.
 > downtime, so you should always have a fallback system available during the
 > upgrade to ensure broadcast continuity.
 
-Before upgrading a production LibreTime server, you should back up both the
-PostgreSQL database and the storage server used by LibreTime. This is especially
-important if you have not already set up a regular back up routine. This extra
-back up is a safety measure in case of accidental data loss during the upgrade,
-for example due to the wrong command being entered when moving files. See
-[Backing up the server](/docs/backing-up-the-server) in this manual for details
-of how to perform these back ups.
-
-The LibreTime [installation script](/install) will detect an existing LibreTime
-deployment and back up any configuration files that it finds. We recommend
-taking your own manual backups of the configuration yourself nevertheless. The
-install script also tries to restart the needed services during an upgrade. In
-any case you should monitor if this happened and also take a quick look at the
-logs files to be sure everything is still fine. Now might be the time to reboot
-the system or virtual machine LibreTime is running on since regular reboots are
-part of a healthy system anyway.
-
-After the upgrade has completed, you may need to clear your web browser's cache
-before logging into the new version of the LibreTime administration interface.
-If the playout engine starts up and detects that a show should be playing at the
-current time, it will skip to the correct point in the current item and start
-playing.
+1. Take a [backup of the server](/docs/backing-up-the-server). This is
+   especially important if you have not already set up a regular back up routine.
+   This extra back up is a safety measure in case of accidental data loss during
+   the upgrade, for example due to the wrong command being entered when moving
+   files. It is also recommended to backup all the configuration files under
+   `/etc/airtime/`.
+2. Run `./install -fiap` as described in the [install documentation](/install).
+   This will detect an existing LibreTime deployment and backup any
+   configuration files that if finds. The install script also tries to restart
+   the needed services during an upgrade. In any case you should monitor if this
+   happened and also take a quick look at the logs files to be sure everything
+   is still fine. Now might be the time to reboot the system or virtual machine
+   LibreTime is running on since regular reboots are part of a healthy system
+   anyway.
+3. Log into the new version of the LibreTime administration interface. If the
+   playout engine starts up and detects that a show should be playing at the
+   current time, it will skip to the correct point in the current time and start
+   playing. If you encounter issues trying to connect to the new administration
+   interface, you may need to clear your web browser's cache.
 
 > **Note:** Airtime's _linked files_ and _watched folders_ features currently do
 > not work in Libretime.

install

@@ -146,8 +146,7 @@ function systemInitDetect() {
     verbose "\nDetecting init system type ..."
     # Get the path of the command where pid=1 following any symlinks
     pid_1_path=$(readlink --canonicalize -n /proc/1/exe)
-    # returns '/sbin/init' (Debian Wheezy & Ubuntu Trusty)
-    # returns '(/usr)?/lib/systemd/systemd' (Debian Stretch, Debian Jessie, Debian Buster, Ubuntu Xenial, CentOS 7)
+    # returns '(/usr)?/lib/systemd/systemd' (Debian Buster, CentOS 7)
     verbose "Detected path to PID=1 process: $pid_1_path"
     # Get package of PID=1 path as it identifies the init system.
     # Allow this to fail, at least then the init system can be guessed from the
@@ -724,11 +723,6 @@ if [ "$ignore_dependencies" = "f" ]; then
         # Get apt-get version by returning the 2nd parameter from the 1st line of output
         apt_version=$(apt-get --version |awk 'NR == 1 { print $2 }')
         # returns 1.8.0~alpha3 (Debian Buster)
-        # returns: 1.4.7 (Debian Stretch)
-        # returns: 0.9.7.9 (Debian Wheezy)
-        # returns: 1.0.1ubuntu2 (Ubuntu Trusty)
-        # returns: 1.0.9.8.4 (Debian Jessie)
-        # returns: 1.2.9 (Ubuntu Xenial)
         verbose "Detected apt-get version as: $apt_version"
         apt_version_formatted=$(awk 'BEGIN {FS = "."} {printf "%03d.%03d\n", $1,$2}' <<<  $apt_version)
         [[ "$apt_version_formatted" < "001.001" ]] && apt_force_options="--force-yes"