Congegni
/
sintonia
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: remove references to deleted obselete instalation methods

This commit is contained in:
ryan 2018-11-21 13:04:56 -06:00
parent fd5587cd81
commit 954713763a
2 changed files with 10 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
docs/manual/upgrading/index.md
View File

@ -1,5 +1,6 @@
LibreTime 3.x versions support upgrading from Airtime 2.5.x versions. LibreTime
follows the [Semantic Versioning (semver)](http://semver.org/spec/v2.0.0.html) standards.
## LibreTime versioning
LibreTime 3.x versions support upgrading from Airtime 2.5.x versions. LibreTime follows the [Semantic Versioning (semver)](http://semver.org/spec/v2.0.0.html) standards.
In a nutshell, given a version number MAJOR.MINOR.PATCH we increment the:
@ -7,45 +8,17 @@ 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.
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.
## Upgrading
If you have deployed LibreTime using the method shown in [Automated installation](../automated-installation/),
you can upgrade in the same way. A new LibreTime package available in
the repository can be installed with:
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.
sudo apt-get update
sudo apt-get upgrade
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.
If you have used the method shown in [Manual installation](../manual-installation/), you should
repeat the installation steps of downloading and unpacking the tarball to an
installation directory, or pulling from the git repository with `git pull`, and
running the `./install` script. The installation script 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.
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.
The install script 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.
There will be tested ways to switch from a LibreTime pre-release to a packaged version
of LibreTime.
There will be tested ways to switch from a LibreTime pre-release to a packaged version of LibreTime.
Airtime 2.5.x versions support upgrading from version 2.3.0 and above. If you are
running a production server with a version of Airtime prior to 2.3.0, you should

3
docs/manual/using-the-airtime-import-script/index.md
View File

@ -41,8 +41,7 @@ Airtime 2.5 for Broadcasters
- **Installation**
- [Preparing the server](../preparing-the-server/index.html)
- [Easy setup](../easy-setup/index.html)
- [Automated installation](../automated-installation/index.html)
- [Manual installation](../manual-installation/index.html)
- [Installation](../install)
- [Setting the server time](../setting-the-server-time/index.html)
- **Administration**
- [Preparing media for ingest](../preparing-media-for-ingest/index.html)