+
In This Section
+-
+ {% for doc in site.docs %}
+ {% if doc.category == page.category %}
+
- {{doc.title}} + {% endif %} + {% endfor %} +
+ + +
Help improve this page
+diff --git a/.gitignore b/.gitignore index fb7037ec1..615c2e240 100644 --- a/.gitignore +++ b/.gitignore @@ -18,4 +18,5 @@ airtime_mvc/tests/log/*.log .idea/ /docs/_site/* /docs/.jekyll-cache/* -/docs/.gems/* \ No newline at end of file +/docs/.gems/* +Gemfile.lock \ No newline at end of file diff --git a/airtime_mvc/application/configs/constants.php b/airtime_mvc/application/configs/constants.php index fb854d113..b82bb65cf 100644 --- a/airtime_mvc/application/configs/constants.php +++ b/airtime_mvc/application/configs/constants.php @@ -19,7 +19,7 @@ define('FAQ_URL' , 'http://libretime.org/faq'); define('WHOS_USING_URL' , 'https://github.com/orgs/LibreTime/people'); define('TERMS_AND_CONDITIONS_URL' , 'https://github.com/LibreTime/libretime/blob/master/README.md'); define('PRIVACY_POLICY_URL' , 'https://github.com/LibreTime/code-of-conduct/blob/master/CODE_OF_CONDUCT.md'); -define('USER_MANUAL_URL' , 'http://libretime.org/'); +define('USER_MANUAL_URL' , 'http://libretime.org/docs'); define('ABOUT_AIRTIME_URL' , 'http://libretime.org'); define('LIBRETIME_CONTRIBUTE_URL' , 'https://libretime.org/contribute'); define('LIBRETIME_DISCOURSE_URL' , 'https://discourse.libretime.org'); diff --git a/airtime_mvc/application/controllers/LocaleController.php b/airtime_mvc/application/controllers/LocaleController.php index e1c1a0e77..cbec559ce 100644 --- a/airtime_mvc/application/controllers/LocaleController.php +++ b/airtime_mvc/application/controllers/LocaleController.php @@ -477,7 +477,7 @@ final class LocaleController extends Zend_Controller_Action "Disabled" => _("Disabled"), "Cancel upload" => _("Cancel upload"), "Type" => _("Type"), - "Autoloading playlists' contents are added to shows one hour before the show airs. More information" => _("Autoloading playlists' contents are added to shows one hour before the show airs. More information"), + "Autoloading playlists' contents are added to shows one hour before the show airs. More information" => _("Autoloading playlists' contents are added to shows one hour before the show airs. More information"), "Podcast settings saved" => _("Podcast settings saved"), "Are you sure you want to delete this user?" => _("Are you sure you want to delete this user?"), "Can't delete yourself!" => _("Can't delete yourself!"), diff --git a/airtime_mvc/application/layouts/scripts/layout.phtml b/airtime_mvc/application/layouts/scripts/layout.phtml index 1b12a6e0c..3267c5e44 100644 --- a/airtime_mvc/application/layouts/scripts/layout.phtml +++ b/airtime_mvc/application/layouts/scripts/layout.phtml @@ -76,14 +76,6 @@ navigation()->menu(); ?> -
Page not found :(
-The requested page could not be found.
- Back to Docs - -+
Help improve this page
+- Basic guides for broadcasting with Libretime can be found here, perfect for DJs. -
- {% for item in site.data.nav.djguides %} -- Program Managers, sometimes known as Program Directors, manage DJs and are responsible for maintaining the station's on-air calendar. All the help Program Managers need is right here. (Note: guides for DJs will also be helpful for programming Libretime) -
- {% for item in site.data.nav.managerguides %} -- System administrators can find all of the information they need here to configure and maintain their LibreTime instance. -
- {% for item in site.data.nav.adminguides %} -- Calling all developers! Find the information you need to get started at the links below. -
- {% for item in site.data.nav.devguides %} -From designing intelligent & automated playlists to drag-and-drop visual editing & cuing, managing your library and playlists has never been simpler.
+Schedule your live and pre-programmed shows easily with a drag-and-drop style calendar, additionally all content broadcasted is logged for efficient reporting to media licensing authorities.
+Libretime's user management allows for the simple creation of hierarchical staff who can control their broadcast slots associated with them from anywhere on the planet!
+LibreTime is flexible, allowing you to run your internet radio station entirely from a cloud VM with its built-in Icecast server or plug its analog output into the mixer at your broadcast AM or FM station.
+- {{ site.headsubtext}} -
- {{ site.headbuttontext }} -- LibreTime is Free/Libre and Open Source (FLOSS) radio automation and broadcasting solution helping communities both modernize their broadcasting stack, and get up and on-the-air with ease. -
-- The platform consists of several open-source components that can be easily and rapidly deployed on both dedicated hardware, virtual machines, and Cloud native infrastructure - allowing your station to truly underwrite it's own destiny. -
-- The platform is a fork of the older AirTime project which is no longer actively maintained, and the evolution of Open Source broadcasting for both current AirTime and new users looking to continue with the platform on their own infrastructure. -
- Key Features -From designing intelligent & automated playlists to drag-and-drop visual editing & cuing, managing your library and playlists has never been simpler.
-Schedule your live and pre-programmed shows easily with a drag-and-drop style calendar, additionally all content broadcasted is logged for efficient reporting to media licensing authorities.
-Libretime's user management allows for the simple creation of hierarchical staff who can control their broadcast slots associated with them from anywhere on the planet!
-LibreTime is flexible, allowing you to run your internet radio station entirely from a cloud VM with its built-in Icecast server or plug its analog output into the mixer at your broadcast AM or FM station.
-
- Requires: 1 Ghz processor, 2 GB RAM, wired ethernet connection with static IP address and you.
What are you waiting for?
-
All of the guides you need to set up, maintain, and use Libretime, all in one place.
+Get Libretime up and running in just 10 minutes.
+Prepare Libretime for primetime.
+Putting in your first show? Start here.
+Learn how to add, change, and delete user accounts.
+Love what we do? Help us out!
+Something not working? Here's a quick guide to fixing Libretime.
+Ask for help on our Github repo!
+sudo bash install -fiap
.
+ linkto: https://github.com/LibreTime/libretime/releases/download/3.0.0-alpha.8/libretime-3.0.0-alpha.8.tar.gz
+ linktext: Download 3.0-alpha-8
+- title: Rolling Commits
+ text: Want the latest and greatest? Install from the source code.
+ linkto: /install
+ linktext: Install from Source
+---
+
+# BROADCAST WITHOUT LIMITS
+
+Libretime is an open source radio automation and broadcasting solution helping communities get on-air with ease.
+
+The platform can be easily deployed on dedicated hardware and VMs, on-prem or in the cloud, "free as in freedom" free.
+
+Let your station underwrite its own destiny.
\ No newline at end of file
diff --git a/docs/install.md b/docs/install.md
deleted file mode 100644
index 7ef4f9a1b..000000000
--- a/docs/install.md
+++ /dev/null
@@ -1,656 +0,0 @@
----
-title: Install
-layout: default
-git: install.md
----
-
-> Note: this guide is assuming you are using Ubuntu 18.04 LTS for installation, which comes with `ufw` and `netplan`,
-and that you have already installed `git` and configured `ntp`. NTP configuration instructions can be found [here](#configuring-ntp).
-While it is possible to install LibreTime on other OSes, such as CentOS 7, Debian 9 and 10, and Raspbian 9 and 10,
-these are less tested. Firewall and static IP address configuration will need to be done according to your OSes instructions.
-
-## Minimum System Requirements
-
-| On-Premises Install | Cloud Install |
-|---------------------|---------------|
-| (FM + Internet Radio) | (Internet Radio Only) |
-| 1 Ghz Processor| 1vCPU |
-| 2 GB RAM | 2 GB RAM |
-| Wired ethernet connection, static IP address | 2 TB of data transfer/month |
-
-[DigitalOcean](https://www.digitalocean.com/pricing/#Compute) and [Linode](https://www.linode.com/pricing/#row--compute)
- have similar plans that meet Cloud Install requirements. Both plans cost $10/month.
-
-## Preparing the server
-
-Configure the server to have a static IP address by modifying the Netplan configuration.
-If you're using a cloud VM, you likely already have a static IP address. Check with your provider to confirm this.
-
-```
-cd /etc/netplan && ls # find the netplan filename
-sudo nano ##-netcfg.yaml
-```
-
-If the Netplan configuration is empty, fill in the file with the example below. Otherwise,
-input the IP address reserved for the server in `xxx.xxx.xxx.xxx/yy` format, the gateway (the IP address
-of your router), and the DNS nameserver. If you don't have a nameserver on your network,
-feel free to use Cloudflare's: `1.1.1.1` and `1.0.0.1`.
-
-```
-network:
- version: 2
- renderer: networkd
- ethernets:
- enp3s0:
- addresses: [192.168.88.8/24]
- gateway4: 192.168.88.1
- nameservers:
- addresses: 192.168.88.1
-```
-
-After the netplan file has been saved, run `sudo netplan apply` to apply changes.
-
-Next, configure Ubuntu's firewall by running:
-
-```
-sudo ufw enable
-sudo ufw allow 80/tcp
-sudo ufw allow 8000/tcp
-```
-
-Unblock ports 8001 and 8002 if you plan to use LibreTime's Icecast server to broadcast livestreams without an external Icecast server acting as a repeater.
-
-```
-sudo ufw enable 8001/tcp
-sudo ufw enable 8002/tcp
-```
-
-> If needed, instuctions for setting up a reverse proxy can be found [here](quickstart#reverse-proxy).
-
-### Installing LibreTime
-
-Installing LibreTime consists of running the following commands in the terminal:
-
-```
-git clone https://github.com/LibreTime/libretime.git
-cd libretime
-sudo ./install -fiap
-```
-
-After the install is completed, head to the IP address of the server LibreTime was just installed on
-to complete the welcome wizard. While not strictly necessary, it is recommended that you change the passwords prompted in the welcome wizard if you intend on accessing the server from the Internet. The welcome wizard will
-walk you through the rest of the installation process.
-
-### Services
-
-Once all of the services needed to run LibreTime are installed and configured,
-it is important that the server starts them during the boot process, to cut down on downtime, especially in live enviornments.
-Ubuntu 18.04 uses the `systemctl` command to manage services, so run the following commands to enable all
-LibreTime-needed services to run at boot:
-
-```
-sudo systemctl enable libretime-liquidsoap
-sudo systemctl enable libretime-playout
-sudo systemctl enable libretime-celery
-sudo systemctl enable libretime-analyzer
-sudo systemctl enable apache2
-sudo systemctl enable rabbitmq-server
-```
-
-If an error is returned, try adding `.service` to the end of each command. For example:
-
-```
-sudo systemctl enable apache2.service
-```
-
-### User Permissions
-
-If you plan to have LibreTime output analog audio directly from its server to a mixing console or transmitter,
-the `www-data` user needs to be added to the `audio` user group using the command below.
-
-```
-sudo adduser www-data audio
-```
-
----
-
-## Reverse Proxy {#reverse-proxy}
-
-In some deployments, the LibreTime server is deployed behind a reverse proxy,
-for example in containerization use-cases such as Docker and LXC. LibreTime
-makes extensive use of its API for some site functionality, which causes
-[Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)
-to occur. By default, CORS requests are blocked by your browser and the origins
-need to be added to the **Allowed CORS URLs** block in
-[**General Settings**](settings). These origins should include any
-domains that will be used externally to connect to your reverse proxy that you
-want handled by LibreTime. These URLS can also be set during the first run configuration
-that is displayed when you first install LibreTime
-
-### Reverse Proxy Basics
-
-A reverse proxy allows the LibreTime server to not be connected to the open internet. In
-this configuration, it is rather behind another server that proxies traffic to it from
-users. This provides some advantages in the containerization space, as this means that
-the containers can be on their own internal network, protected from outside access.
-
-A reverse proxy also allows SSL to be terminated in a single location for multiple sites.
-This means that all your traffic to the proxy from clients is encrypted, but the reverse
-proxy's traffic to the containers on the internal network is not. All the SSL certificates
-live on the reverse proxy and can be renewed there instead of on the individual
-containers.
-
-### Setup
-
-There are known bugs when using LibreTime behind a reverse proxy ([#957](https://github.com/LibreTime/libretime/issues/957)
-tracks the issue and contains a temporary workaround). For SSL redirection to work, you
-need two domains: one for LibreTime and one for Icecast. Here, these will be
-`libretime.example.com` and `icecast.example.com`.
-
-You will also require two VMs, servers or containers. Alternatively the reverse proxy can
-be located on the server, proxying connections to containers also on the host. Setting up
-a containerization environment is beyond the scope of this guide. It assumes that you have
-Nginx set up on `proxy` and LibreTime will be installed on `libretime`. You will need root
-access on both. `libretime` also needs to be able to be accessed from `proxy`
-(`ping libretime` on `proxy`).
-
-On `libretime`, install LibreTime as described in the [install guide](quickstart). In short
-this means run the following commands:
-
-```
-git clone https://github.com/LibreTime/libretime.git
-cd libretime
-sudo ./install -fiap
-```
-
-Once it has installed, replace `