From 34d7c1ccf0fbd1c47574f9691b155251d9690214 Mon Sep 17 00:00:00 2001 From: Zachary Klosko <31484611+zklosko@users.noreply.github.com> Date: Fri, 15 May 2020 13:03:15 -0400 Subject: [PATCH] Fixing broken links --- docs/tracks.md | 2 +- docs/upgrading.md | 11 +++++++++-- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/tracks.md b/docs/tracks.md index 61d59612a..92eb4f71c 100644 --- a/docs/tracks.md +++ b/docs/tracks.md @@ -30,7 +30,7 @@ indicate if a particular item is in use). To change the fields which can be searched, click the **Show / hide columns** button on the right side of the table, just above the search results. -![](../dashboard/img/columns.png) +![](img/columns.png) Click the metadata column headings such as **Title**, **Creator**, **Album**, or **Genre** to sort the entries in ascending or descending order. In the second diff --git a/docs/upgrading.md b/docs/upgrading.md index 0c0392328..5d009c8bd 100644 --- a/docs/upgrading.md +++ b/docs/upgrading.md @@ -10,11 +10,18 @@ In a nutshell, given a version number MAJOR.MINOR.PATCH we increment the: 2. MINOR version when we add functionality in a backwards-compatible manner, and 3. PATCH version when we make backwards-compatible bug fixes. -Any pre-release versions of LibreTime are denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. This pre-release indicates that the version is unstable in a sense that it might contain incomplete features or not satisfy the intended compatibility requirements as per semver. +Any pre-release versions of LibreTime are denoted by appending a hyphen and a series +of dot separated identifiers immediately following the patch version. This pre-release indicates +that the version is unstable in a sense that it might contain incomplete features or not satisfy the +intended compatibility requirements as per semver. ## Upgrading -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](../backing-up-the-server/) in this manual for details of how to perform these back ups. +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](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 or Airtime 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.