Skip to content

Installation and basic set-up

This information is for technicians and may be difficult to understand if you have little or no experience setting up web applications. In that case, you may wish to seek help or point your organisation's technical staff to this material.

Prerequisites

CiviCRM must be installed on a computer with a web server (such as Apache or nginx), PHP and MySQL. Some prefer to try CiviCRM on their local computer before installing it on a dedicated web server. If you don't have these prerequisites, you can download packages from the Internet such as WAMP, XAMPP, MAMPP and LAMP. The first two packages are for Windows and the second two are for the Macintosh and Linux, respectively.

Consider where you host your CiviCRM instance. Discuss hosting with your System Administrator and review the Hosting information in the System Admin guide.

Before installation, decide which CMS (Content Management System: used for building and managing websites) you wish to integrate with. The open-source options are Drupal, WordPress and Joomla!, or you can use Standalone CiviCRM.

You can find full installation instructions in the System Administrator Guide.

Internet vs. local installs

Most organisations access CiviCRM over the internet. Some organizations that only want internal staff to have access, and are security conscious, choose to install CiviCRM on an internal network where it is accessible only internally. The downside of an installation that is not publicly available is that contacts cannot 'self serve' to update their data.

Securing your system

Once CiviCRM is installed, it is important to secure your system. The System Administrator Guide describes techniques for securing your server and website.

Upgrades

New versions of CiviCRM are released every month. Although extensions are typically how you add major new features, you need to upgrade the CiviCRM core software periodically to keep your site secure and take advantage of smaller new features and improvements. Some upgrades contain security fixes that are crucial to apply in a timely manner.

Plan for the people and time needed to upgrade your site. Read release notes thoroughly to understand how an upgrade may change it. Test upgrades on a copy of your live site to make sure the process runs smoothly. Back up your site and database before upgrading your live site, even if you tested the process on a test site.

Because upgrades are important and technical, many organisations employ a CiviCRM expert service provider to carry them out.