This document explains how to import services from another control panel into MediaCP.
It also explains how to upgrade from our ShoutcastCP to the MediaCP.
ShoutcastCP - Importing / Upgrading
The MediaCP is a seperate product, not an upgrade - therefore you will need to install the MediaCP and import your ShoutcastCP services. This document will explain this.
- Backup ShoutcastCP Files
Create a new directory, for instance /pathto/shoutcastcp/scp.bak/ and move all the ShoutcastCP file into this for safe keeping.
- Disable ShoutcastCP
You should disable the cron job that currently exists for the ShoutcastCP.
(Do not disable the cron for the MediaCP)
For the MediaCP, the cron job is always installed in /etc/crontab however for the ShoutcastCP, this was up to the whoever installed the panel.
You may need to look around to find where the cron job is installed - on most systems you can run the following to determine if any cron jobs are running:
# tail /var/log/cron
- Install MediaCP
Install MCP to the same location as ShoutcastCP was.
Once installed, do not create any new users or services - the import will not work if you do this.
- Copy the ShoutcastCP Contents Directory
To import media files, you will need to copy or move the [ShoutcastCP]/content directory into your MediaCP.
With Windows Server, you can simply copy/move the contents directory by dragging and dropping.
For Linux, you can use the "cp" utility like below (the "-a" will copy recursively:
# cp -a /path/to/shoutcastcp/content/* /pathto/mediacp/content/
# chmod 777 /pathto/mediacp/content/
- Launch the Import Script
Open http://yourdomain/mediacp/other/import/shoutcastcp.php from your browser.
Follow the prompts and enter your ShoutcastCP Database details here.
You can find these by issuing "more /pathto/shoutcastcp/database.php"
- Restart Services
It is advised to manually kill all shoutcast process and restart them in the MediaCP.
# killall sc_serv; killall sc_trans
If all went well, your MediaCP should now contain all your media services.
If you have difficulties with the MediaCP, please review the Troubleshooting section of the documentation.