|Automated Installer for Standalone CiviCRM 2.2|
This page provides instructions for using the web-based Automated Installer.
Before beginning this upgrade, verify that your server meets the requirements for CiviCRM 2.2.
- CiviCRM 2.1.x : You must be running CiviCRM 2.1.x to use this upgrade.
- PHP 5.x : Starting with the 1.9 release, CiviCRM will NOT run on PHP4 servers* (more info...).
- MySQL 5.0.x or higher : CiviCRM is compatible the current generally available MySQL release.
If you are upgrading from v2.1 to v2.2 - use these instructions.
1. Server Requirements
CiviCRM 2.2 Standalone has been developed and tested on the following 'recommended' platforms:
- Linux (especially Ubuntu and Red Hat / CentOS)
- Apache 2.x
- PHP 5.2.1 (or newer)
- MySQL 5.x
Caution: Under Linux, the optional CiviMail component requires PHP with SOAP and DOM extensions, Postfix 2.2 (a mailer), and Perl 5.8.X. (more info...)
2. Linux/UNIX installation
These instructions are based on an Ubuntu Linux installation (version 8.04 "hardy" is your best bet) and I've included tips for Red Hat / CentOS 5 in a few places too. Your mileage may vary on other distros / Unices.
Follow these steps:
- Install Apache, MySQL 5 (server and client), and PHP5.
- Ubuntu / Debian installation command:
- Red Hat / CentOS / Fedora - You may have to install PHP's XML support package, like so:
- Download the latest release version of CiviCRM 2.2 to your home directory. As of version 2.2.7, there is a standalone tarball, so grab that. (Prior to 2.2.7, you would have used the drupal tarball.)
- Make sure the tarball is in your home directory on your Linux system. If you're uploading it to a remote web server, usually you can just put it in the first directory your FTP client drops you into.
- Untar the archive to your web-root (defaults to /var/www/ on Ubuntu and /var/www/html on Red Hat / CentOS). You'll need to get a shell on your Linux system if you don't already have one. Usually this is done via SSH for a remote web server or by running a Terminal if you're using a Linux system locally.
It is generally considered bad security practice to put an entire system like CiviCRM under the docroot of a web server. This exposes a lot of files and code to potential hackers that really isn't necessary. If you're just testing CiviCRM Standalone on a machine that isn't accessible from the Internet, it's probably not a big deal. But don't even think about setting up a live production server without following these directions.
- Set the directory ownerships correctly (use whatever user your system runs Apache as, on Ubuntu that's "www-data" as shown below; Red Hat/Fedora/CentOS use "apache" instead):
- Run the installer by visiting the url (replace "localhost" with the address of your web server if doing a remote installation): http://localhost/civicrm/install/index.php?mode=standalone
The installer will verify that you've downloaded the correct version of CiviCRM, and will check your server environment to make sure it meets CiviCRM requirements. It will then create and populate a database for CiviCRM as well as create your CiviCRM settings file (civicrm.settings.php).
Successful installation will redirect you to Step 5 i.e Standalone first user (Admin) setup process.
Note: You can access your new CiviCRM installation in your web browser (replace "localhost" with the address of your web server if doing a remote installation): http://localhost/civicrm/standalone/index.php
3. Mac OS X installation
4. Windows installation
5. Common steps for all platforms
Congratulations! You've finished the hard parts of installing CiviCRM. Now you just need to finish up some housekeeping and you'll be managing your constituent relationships like a pro in no time.
- You should now see a page that says "CiviCRM First User Setup". If you got an error about the civicrm schema already existing in the MySQL server, then you need to drop the civicrm database from your MySQL server. There are a number of ways to do that, but be very careful that you are not deleting data you'd rather keep! Dropping the database will permanently delete whatever was in there before. That's why the installer doesn't offer to do it for you. Backing it up first is almost always a good idea.
- Setup your first user. You'll need an OpenID, which you can get from myopenid.com (among other places) if you don't have one. If you have an AIM account, then you already have one: http://openid.aol.com/your-aim-username
- After you log in, you'll be asked to setup your new user record. This record identifies you in the system, so be as detailed as possible.
- Once you're finally seeing the CiviCRM dashboard page, you'll probably want to configure the resource URL so that the CSS and images load correctly. This will make everything much less ugly.
- Click Administer CiviCRM, then click Global Settings (it's about halfway down the page), then click Resource URLs.
- In the top "CiviCRM Resource URL" box, replace the URL that's in there with this: http://yourserver.com/civicrm/