logs and service names need documentation

[frecuencialibre]

the libretime troubleshooting docs don't apply to this docker install. two parts:

1. LOGS:
   i see some in /var/log/supervisor and some in /var/log/airtime. and then there are docker logs. is that it?

2. SERVICES:
   we should document their names ( libretime-airtime_analyzer? etc.) and how check their status/restart them, ie. what's the best replacement for invoke-rc.d?

@ned-kelly if you can give me some guidance here i'd take a crack at drafting this.

[frecuencialibre]

basically one uses the CLI provided by Supervisor. For example, to see the status of all processes, try:

supervisorctl

tutorial

@ned-kelly correct? if so let's close this one.

[ned-kelly]

Hi @frecuencialibre - yep, the docker build is using supervisor - It's probably worth quickly skimming over the supervisor docs here.

You can also access the interactive supervisor shell by running docker exec -it libretime-core bash -c "supervisorctl".

On the subject of accessing logs, it's probably also worth adding in that all services log to the stderr/stdout of the docker container, so it's best to easily access logs using the docker daemon i.e. docker logs -f libretime-postgres (I realise, however you may need to access the supervisor logs and/or supervisor daemon to restart one of the libretime services running within the core libretime daemon, access it's logs etc (i.e. docker exec -it libretime-core bash -c "supervisorctl tail apache2").

Hope this helps shed some light.