EasyApache3 Saving Custom Options
Every time Apache is rebuilt, its current configuration is stored as Previously Saved Config, in both the command line and WHM EasyApache interfaces. However, you may still want to store your custom configuration for later use.
To store custom options, you should save the configuration with a file name, display name, and description. You can accomplish this under step 6 in EasyApache, by filling in the required information and clicking Save and build or Save only (Do NOT build). Using the Save only (Do NOT build) button can be useful if you would like to create a profile for a different server.
The custom profile is saved to the
/var/cpanel/easy/apache/profile/custom/
directory on your server, and automatically given the filename extension .yaml.
SpamAssassin Rules Updates
This feature defines how you would like to update SpamAssassin rules.
Automatic — Automatically update SpamAssassin rules whenever /usr/local/cpanel/scripts/upcp runs.
Manual Updates Only — Requires you to manually run /usr/local/cpanel/scripts/upcp to update SpamAssassin rules.
NEVER Update — SpamAssassin rules do not update when /usr/local/cpanel/scripts/upcp runs.
Cpanel Release Tiers
cPanel has released publicly in 4 tiers:
* STABLE
* RELEASE
* CURRENT
* EDGE
This scheme allows rapid development and quick availability of new versions of cPanel & WHM. Server admins can select a cPanel & WHM tier.
STABLE Has received considerable public exposure, testing, and verification. Published least frequently.
RELEASE Similar to STABLE, but has received slightly less testing. Updated more often than STABLE. New installations default to RELEASE. Published more frequently than STABLE.
CURRENT Tested and verified, but may not contain all proposed functionality of a release. Similar to the “release candidate” tier used under other publication schemes.
EDGE Has received only rudimentary testing. Features are subject to further modification. Usually lacks official public documentation.
Due to the dynamic nature of EDGE builds, you should only use EDGE for compatibility and functionality testing in a controlled environment. Do not use the EDGE tier on production servers.
Reference: http://cpanel.net/
Updating RubyGems
You will have to manually update any RubyGems that is installed.
Run
/usr/local/cpanel/scripts/installruby
WHM will install only required modules.
It will update these modules when /usr/local/cpanel/scripts/upcp runs.
Updating cPAddons
cPAddons: Pieces of software that you can install on your website through cPanel. cPAddons provide useful tools to your website. Common examples include bulletin boards, chat programs, and online shopping carts.
You can manage specific configuration options for your cPAddons using the Manage cPAddons feature located at
Main >> cPanel >> Manage cPAddons in your WHM interface.
This feature will allow you to choose which cPAddons you wish to update automatically.
These cPAddons are updated by a cronjob that runs nightly. This cronjob updates the cPAddon repository for the entire server.
