Parallels Plesk Panel Server backup repository
Server backup repository location.
As of Parallels Plesk Panel version 9.0, the structure and location of the server backup repository have both changed.
The root backup directory is now stored in the file /etc/psa/psa.conf, while it is still set by the variable DUMP_D as before:
Backups directory
DUMP_D /var/lib/psa/dumps
Server backups, backups of resellers, clients, domains, and daily MySQL dumps are now stored in this directory.
Adding RPM Fusion Repository
Command Line Setup using rpm
To enable access to both the free and the nonfree repository use the following command:
Fedora 15, 16 and 17:
su -c ‘yum localinstall –nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm’
RHEL 6 or compatible like CentOS:
su -c ‘yum localinstall –nogpgcheck http://download1.rpmfusion.org/free/el/updates/6/i386/rpmfusion-free-release-6-1.noarch.rpm http://download1.rpmfusion.org/nonfree/el/updates/6/i386/rpmfusion-nonfree-release-6-1.noarch.rpm’
Repository Structure Parallels Plesk Panel for Linux/Unix
The Parallels Plesk Panel for Linux/Unix repository located at http://autoinstall.plesk.com is structured as follows.
* products.inf3 - Parallels Installer configuration file which describes the Panel products
* plesk.inf3 - Parallels Installer configuration files which describe different versions of the Panel and additional components.
* pp-sitebuilder.inf3 - The configuration file which describes SiteBuilder - the required Panel component.
* billing.inf3 - The configuration file which describes Customer & Business Manager - the Panel component.
* [PRODUCT_NAME]_[product_version] - Several subdirectories named in accordance with the Panel versions.
Reference: http://parallels.com/
From time to time the RubyGems repository will be unavailable. If at any point during installation process the RubyGems repository becomes unavailable, you will need to re-run
Since Ruby on Rails uses its own web server, it has to run this web server on an alternate port. This causes an issue if you are running a firewall on your system. You will need to ensure that ports 12001 and up are open. We recommend making the max number of the open ports 12001 plus whatever the number of Ruby applications you expect to be running will be.
