From e877cf6498c8e697f82ab7573c66605a8dc37bf3 Mon Sep 17 00:00:00 2001 From: Zachary Klosko Date: Wed, 1 Jul 2020 10:56:16 -0400 Subject: [PATCH] Finishing up PR --- docs/404.html | 32 +------------------------- docs/_layouts/404.html | 43 +++++++++++++++++++---------------- docs/backing-up-the-server.md | 6 ++--- docs/microsite.md | 4 +++- docs/preparing-media.md | 4 ++-- docs/troubleshooting.md | 34 +++++++++++++++------------ 6 files changed, 50 insertions(+), 73 deletions(-) diff --git a/docs/404.html b/docs/404.html index b32415f9e..81dc7a640 100644 --- a/docs/404.html +++ b/docs/404.html @@ -1,34 +1,4 @@ --- permalink: /404.html layout: 404 ---- - - - -
-
- 404 Tape - -

Page not found :(

-

The requested page could not be found.

- - - Back to Docs - -
-
\ No newline at end of file +--- \ No newline at end of file diff --git a/docs/_layouts/404.html b/docs/_layouts/404.html index de1d54cf3..d57fe6438 100644 --- a/docs/_layouts/404.html +++ b/docs/_layouts/404.html @@ -3,7 +3,19 @@ {% include head.html %} - {{ site.title }} - {{ page.title }} @@ -13,28 +25,19 @@ {% include navbar.html %} - - - - - - Back to top - -
- +
+ 404 Tape +

Page not found :(

+

The requested page could not be found.

+ + + Back to Docs + +
- + {% include footer.html %} {% include scripts.html %} diff --git a/docs/backing-up-the-server.md b/docs/backing-up-the-server.md index 9b3b7fb45..4ecc57540 100644 --- a/docs/backing-up-the-server.md +++ b/docs/backing-up-the-server.md @@ -67,12 +67,10 @@ the backup server also contains an LibreTime installation, it should be possible to switch playout to this second machine relatively quickly, in case of a hardware failure or other emergency on the production server. -A standard incremental backup tool on GNU/Linux servers is *rsync* -[(http://rsync.samba.org/)](http://rsync.samba.org/)) which can be installed +A standard incremental backup tool on GNU/Linux servers is [rsync](http://rsync.samba.org/) which can be installed using the package manager of your GNU/Linux distribution. However, incremental backup alone cannot help in the scenario where a file which later proves to be important has been deleted by an administrator. For backups that can be rolled back to restore from an earlier date than the current backup, the tool -*rdiff-backup* -[(http://www.nongnu.org/rdiff-backup/](http://www.nongnu.org/rdiff-backup/)) can +[rdiff-backup](http://www.nongnu.org/rdiff-backup/) can be deployed.   diff --git a/docs/microsite.md b/docs/microsite.md index dbfed0246..0705dd465 100644 --- a/docs/microsite.md +++ b/docs/microsite.md @@ -1,9 +1,11 @@ --- layout: default title: Built-in Microsite -git: microsite +git: microsite.md --- +## Overview + ![](img/radio-page.png) LibreTime includes a mini-site, which can be accessed at _serverIP_ (for local installations), or diff --git a/docs/preparing-media.md b/docs/preparing-media.md index e32cbeb07..25395a84e 100644 --- a/docs/preparing-media.md +++ b/docs/preparing-media.md @@ -89,8 +89,8 @@ In the output from vorbisgain, *Peak* is the maximum sample value of the file be ## Silence in media files -Before importing media, it is good practice to check for any silent sections in the media files. While LibreTime compensates for leading and trailing silence with the use of automatic cue-in and cue-out points****, it may be preferable to trim these files to the intended length before upload. This is because media in the LibreTime library could potentially be re-used in many different systems. **Audacity** is a cross-platform editor suitable for the task of trimming audio files, available from [http://audacity.sourceforge.net/](http://audacity.sourceforge.net "http://sourceforge.net/projects/dr14tmeter/") +Before importing media, it is good practice to check for any silent sections in the media files. While LibreTime compensates for leading and trailing silence with the use of automatic cue-in and cue-out points, it may be preferable to trim these files to the intended length before upload. This is because media in the LibreTime library could potentially be re-used in many different systems. There are many cross-platform audio editors, including [Audacity](https://www.audacityteam.org/) and [ocenaudio](https://www.ocenaudio.com/), that are suitable for the task of trimming audio files -Very quiet introductions or over-long fades can also lead to apparent gaps in your broadcast playout. Some audio CDs feature a 'hidden track' at the end, which in fact uses a long period of silence within the final track, rather than an actual separate track on the disc. This means that CD encoding programs will often encode both the hidden material and the silence in the media file. For example, the track "Debra" from the CD *Midnite Vultures* by Beck includes hidden material preceded by seven minutes of silence, as shown in the screen shot from Audacity below. +Quiet introductions or extended fades can also lead to apparent gaps in your broadcast playout. This is more common when playing back audio from ripped CDs or dubbed from tape or vinyl; this issue is not as common with digitally-purchased music. For best results, long periods of silence should be removed from files before uploading to Libretime. ![](img/Screenshot126-Debra_silence.png) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 7594bdd75..a65373835 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1,23 +1,27 @@ --- layout: default title: Troubleshooting - +git: troubleshooting.md --- ## Restarting services LibreTime is effectively a web site running on a LAPP stack, so individual components of the system can be started, stopped, restarted or checked in the server console using the **systemctl** command: - sudo systemctl start|stop|restart|status libretime-liquidsoap - sudo systemctl start|stop|restart|status libretime-playout - sudo systemctl start|stop|restart|status libretime-celery - sudo systemctl start|stop|restart|status libretime-analyzer - sudo systemctl start|stop|restart|status apache2 - sudo systemctl start|stop|restart|status rabbitmq-server +``` +sudo systemctl start|stop|restart|status libretime-liquidsoap +sudo systemctl start|stop|restart|status libretime-playout +sudo systemctl start|stop|restart|status libretime-celery +sudo systemctl start|stop|restart|status libretime-analyzer +sudo systemctl start|stop|restart|status apache2 +sudo systemctl start|stop|restart|status rabbitmq-server +``` For example, to restart the Airtime playout engine, you could enter the command: - sudo systemctl restart libretime-playout +``` +sudo systemctl restart libretime-playout +``` ## Log files {#logs} @@ -62,19 +66,19 @@ If the Airtime logs indicate failures to connect to the RabbitMQ server, such as 2013-10-31 08:21:11,255 ERROR - \[pypomessagehandler.py : main() : line 99\] - Error connecting to RabbitMQ Server. Trying again in few seconds - See more at: http://forum.sourcefabric.org/discussion/16050/\#sthash.W8OJrNFm.dpuf ``` -but the RabbitMQ server is running normally, this error might be due to a change in the server's hostname since Airtime installation. Directory names under */var/lib/rabbitmq/mnesia/* indicate that RabbitMQ's database files are organised according to the hostname of the server, for example: -``` -rabbit@airtime -``` -where the hostname is *airtime.example.com*. If the hostname has changed, it may be necessary to reconfigure RabbitMQ manually, as follows: +but the RabbitMQ server is running normally, this error might be due to a change in the server's hostname since Libretime installation. Directory names under */var/lib/rabbitmq/mnesia/* indicate that RabbitMQ's database files are organised according to the hostname of the server (ex. `rabbit@airtime`) where the hostname is *airtime.example.com*. If the hostname has changed, it may be necessary to reconfigure RabbitMQ manually, as follows: 1. Delete the files in */var/lib/rabbitmq/mnesia/* - sudo rm -r /var/lib/rabbitmq/mnesia/* +``` +sudo rm -r /var/lib/rabbitmq/mnesia/* +``` 2. Restart RabbitMQ: - sudo systemctl restart rabbitmq-server +``` +sudo systemctl restart rabbitmq-server +``` 3. Enter the following commands to set up authentication and grant permissions. The *rabbitmqctl add\_user* command requires the RabbitMQ password from the /etc/airtime/airtime.conf file as an argument. The *rabbitmqctl set\_permissions* command should be entered on one line, with the list of Airtime services repeated three times: