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

docs: update releases notes

Browse source 
- remove duplicate deprecations and upgrade procedures
- add emijeeezz
This commit is contained in:
jo 2022-02-21 15:05:24 +01:00 • committed by Kyle Robbertze
parent 9ebd2c85ef
commit 3f6438383f
17 changed files with 322 additions and 819 deletions
Download patch file Download diff file Expand all files Collapse all files

30
docs/admin-manual/setup/install.md
View file

@ -65,6 +65,17 @@ git clone https://github.com/libretime/libretime
cd libretime
```
:::info
When upgrading, you can pull the latest changes from the repository before checking out the desired version:
```bash
cd libretime
git pull
```
:::
And checkout the latest version:
<CodeBlock language="bash">
@ -88,6 +99,12 @@ Additional options can be listed with the following command:
./install --help
```
:::info
When upgrading be sure to run the installer using the same arguments you used during the initial install.
:::
Once the installation is completed, open [http://localhost:80](http://localhost:80) to complete the [setup wizard](#setup-wizard).
:::note
@ -142,3 +159,16 @@ sudo rabbitmqctl change_password "airtime" "new-password"
```
Once completed, it's recommended to [install a reverse proxy](./reverse-proxy.md) to setup SSL termination and secure your installation.
## Using packages
:::note
Usually the packages are built soon after a release is published.
:::
You can install LibreTime using packages on the distributions listed below, please follow further instruction provided by the links below:
- [Debian / Ubuntu packages](https://github.com/LibreTime/libretime-debian-packaging/releases)
- [CentOS packages](https://build.opensuse.org/package/show/home:radiorabe:airtime/libretime)

19
docs/admin-manual/setup/upgrade.md
View file

@ -7,20 +7,23 @@ This guide walk you though the steps required to upgrade LibreTime.
:::tip
You should always have a fallback system available during the upgrade to ensure **broadcast continuity**.
You should always have proper backups and a rollback scenario in place before updating. If the update does not go smoothly, it may cause significant downtime, so you should always have a fallback system available during the update to ensure **broadcast continuity**.
:::
#### Make a backup
## Make a backup
Follow [the backup guide](../backup.md) to make an extra backup of your installation in case of accidental data loss during
the upgrade process.
Follow [the backup guide](../backup.md) to make an extra backup of your installation and prepare a rollback scenario in case of accidental data loss during the upgrade process.
#### Install the new version
## Install the new version
Follow [the install guide](./install.md) to download and install the new version.
Follow [the install guide](./install.md#download) to download and install the new version, and re-run the `./install` script with the same arguments you used during the initial install.
#### Verify
## Apply upgrade instructions
Be sure to carefully read **all** the [releases notes](../../../releases), from your current version to the targeted version, to apply upgrade or breaking changes instructions to your installation.
## Verify
Verify that all the services are still running after the install process:
@ -37,7 +40,7 @@ sudo systemctl status \
Verify for any error in the logs after the install process:
```bash
sudo tail -n 20 /var/log/libretime/**/*.log
sudo tail -f -n 100 "/var/log/syslog" | grep "libretime-"
```
Log into the interface and verify for any error after the install process.