AzuraCast is powered by Docker and uses pre-built images that contain every component of the software. Don't worry if you aren't very familiar with Docker; our easy installer tools will handle installing Docker and Docker Compose for you, and updates are very simple.
System Requirements:
- A 64-bit x86 (x86_64) CPU
- 2GB or greater of RAM
- 20GB or greater of hard drive space
For Linux hosts, the sudo, curl and git packages should be installed before installing AzuraCast. Most Linux distributions include these packages already.
Installing
Connect to the server or computer you want to install AzuraCast on via an SSH terminal. You should be an administrator user with either root access or the ability to use the sudo command.
Pick a base directory on your host computer that AzuraCast can use. If you're on Linux, you can follow the steps below to use the recommended directory:
mkdir -p /var/azuracast
cd /var/azuracast
Use these commands to download our Docker Utility Script, set it as executable and then run the Docker installation process:
curl -fsSL https://raw.githubusercontent.com/AzuraCast/AzuraCast/master/docker.sh > docker.sh
chmod a+x docker.sh
./docker.sh install
On-screen prompts will show you how the installation is progressing.
Once the installation has completed, be sure to follow the post-installation steps. You can also set up LetsEncrypt or make other changes to your installation using the Docker Utility Script that you've just downloaded.
Post-Installation Tasks
Our administration guide has several pages dedicated to tasks you should complete once your installation is finished:
- Post-installation Setup
- Updating
- Backup & Restore
Post-installation Setup
Once the installation is complete, you should immediately visit your server's public web address. This may be the IP of the server, a domain name (if you've registered one and pointed it at the server), or localhost if you're running AzuraCast on your personal computer.
The initial web setup consists of the following steps:
- Creating a "Super Administrator" account with system-wide administration permissions
- Creating the first radio station that the system will manage
- Customizing important AzuraCast settings, like the site's base URL and HTTPS settings
Updating
Updating AzuraCast
Updating AzuraCast will update both the web app itself and all of its dependencies, so you will be on the latest version of all of the supporting software.
During the update process, your stations will be briefly offline to listeners, so you should set aside a time to update and notify listeners if necessary.
Docker Installations
Using the included Docker utility script, updating is as simple as running:
cd /var/azuracast
./docker.sh update-self
./docker.sh update
By default, the updater will prompt you to update your docker-compose.yml file. If you aren't making any changes to this file and want to automate the update process, you can use the command below to automatically answer "yes" to this question:
cd /var/azuracast
./docker.sh update-self && echo "y" | ./docker.sh update
Switching Update Release Preference
By default, all AzuraCast installations will update to the latest "Rolling Release" version; that is, the very latest changes that have been committed to the main AzuraCast repository. While this will give you access to the very latest features, it also may introduce errors or instability that you may not want in a production radio station.
To switch to only installing stable releases during updates, edit azuracast.env in your host and add or modify this line:
PREFER_RELEASE_BUILDS=true
Ansible Installations
AzuraCast also includes a handy updater script that pulls down the latest copy of the codebase from Git, flushes the site caches and makes any necessary database updates. Run these commands as any user with sudo permissions:
cd /var/azuracast/www
sudo chmod a+x update.sh
sudo ./update.sh
Backup & Restore
Via the Web Interface
The "System Administration" section of your AzuraCast web interface has a dedicated "Backup" page, where you can configure periodic automated backups, run a one-time backup and download existing backup files.
Backups run through the web panel do not interrupt your broadcasts or disconnect your listeners.
Via the Command Line
If you want more control over where your backup files are going, or want to take advantage of pre-existing tools (like cron tasks) to handle the backup, you can use the Docker Utility Tool to generate backups as well.
The most basic version of this command is:
cd /var/azuracast
./docker.sh backup path-to-backup.zip
You can also pass the --exclude-media flag to back up just the database and statistics, but not the media itself, which significantly reduces the backup file size (but you should make sure to back your media up elsewhere):
cd /var/azuracast
./docker.sh backup --exclude-media path-to-backup.zip
Both .zip and .tar.gz formats are supported for backups. The correct format will automatically be determined by the extension of the filename you specify for the backup file.
Restoring a Backup
To restore the backup later, run the following command:
cd /var/azuracast
./docker.sh restore path-to-backup.zip
