ctactic/aircox-radiocampus
1
0
Fork 0
forked from rc/aircox
Code Issues 10 Pull Requests Activity

translation

Browse Source
This commit is contained in:
bkfox
2022-05-21 16:37:11 +02:00
parent 8f0dd9d248
commit 478ce58c17
7 changed files with 361 additions and 271 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -2,16 +2,17 @@
Platform to manage a radio, schedules, website, and so on. We use the power of great tools like Django or Liquidsoap.
This project is distributed under GPL version 3. More information in the LICENSE file, except for some files whose license is indicated.
This project is distributed under GPL version 3. More information in the LICENSE file, except for some files whose license is indicated inside source code.
## Features
* **streams**: multiple random music streams when no program is played. We also can specify a time range and frequency for each;
* **diffusions**: generate diffusions time slot for programs that have schedule informations. Check for conflicts and rerun.
* **liquidsoap**: create a configuration to use liquidsoap as a stream generator. Also provides interface and control to it;
* **sounds**: each programs have a folder where sounds can be put, that will be detected by the system. Quality can be check and reported for later use. Later, we plan to have uploaders to external plateforms. Sounds can be defined as excerpts or as archives.
* **cms**: application that can be used as basis for website;
* **sounds**: each programs have a folder for its podcast. Aircox detects updates, can run quality check, import related playlist (timestamped or position in track list). Sounds can be defined as excerpts or as archives.
* **log**: keep a trace of every played/loaded sounds on the stream generator.
* **admin**: admin user interface.
* **cms**: content management system.
## Scripts
@ -27,8 +28,6 @@ and `gunicorn` in mind.
## Installation
Later we plan to have an installation script to reduce the number of above steps.
### Dependencies
For python dependencies take a peek at the `requirements.txt` file, plus
dependencies specific to Django (e.g. for database: `mysqlclient` for MySql
@ -50,7 +49,7 @@ Development dependencies:
All scripts and files assumes that:
- you have cloned aircox in `/srv/apps/` (such as `/srv/apps/aircox/README.md`)
- you have a supervisor running (we have scripts for `supervisord`)
- you want to use `gunicorn` as WSGI server (otherwise, you'll need to remove it from the requirement list)
- you use `gunicorn` as WSGI server (otherwise, you'll need to remove it from the requirement list)
This installation process uses a virtualenv, including all provided scripts.
@ -87,8 +86,7 @@ server from this directory:
./manage.py runserver
```
You can access to the django admin interface at `http://127.0.0.1:8000/admin`
and to the cms interface at `http://127.0.0.1:8000/cms/`.
You can access to the django admin interface at `http://127.0.0.1:8000/admin`.
From the admin interface:
* create a Station
@ -96,8 +94,6 @@ From the admin interface:
* defines Outputs for the streamer (look at Liquidsoap documentation for
more information on how to configure it)
TODO: cms related documentation here
Once the configuration is okay, you must start the *controllers monitor*,
that creates configuration file for the audio streams using the new information
and that runs the appropriate application (note that you dont need to restart it
@ -107,5 +103,5 @@ If you use supervisord and our script with it, you can use the services defined
in it instead of running commands manually.
## More informations
There are extra informations in `aircox/README.md`.
There are extra informations in `aircox/README.md` and `aircox_streamer/README.md`.