There is no formal installation procedure for aBlog2. Simply download the zip file, unpack it, and put aBlog2 into your web server's space. Where in the space is lives in unimportant, but we recommend at the top level where it can be easily shared by a variety of applications. In all of our examples, we're going to assume that this is where the code is loaded.
Important: If you're going to use aLogin2 for authentication you must also run the aLogin2 setup. If you're not using aLogin you'll need to modify the localAuthority.php file (See Localization).
There are two ways to make aBlog available to an application. You can either run the provided setup script, or you can use a callable function. The later is useful if your application has it's own setup script since the aBlog2 setup can be folded into the larger setup. In either case the setup creates a configuration file that the application can use and copies certain files into the applications folder on the server. You will need to have the following information available:
|Path to the application||This is the path to the location of the application that is going to use aBlog2.|
|The name of the application3||Whatever you want to call the application that is going to use aBlog2.|
|Path to the configuration file||This file will be build automatically during the set up process. The path should include the file name. For security the path should not be located within the web servers data tree but it must be located somewhere that the server can write to.|
|Path to the data library2||This is the path to a file that contains functions for accessing the database. See the page on using the database for details. Two possible libraries are supplied with aBlog, mysql_datalib.php and sqlite_datalib.php. Both are located in the top directory of aBlog2. (./mysql_datallib.php or ./sqlite_datalib.php) If you use sqlite_datalib.php, it will create a file, mapApp.sqlite at the top level of your applications directory.|
|Path to the utility library2||This is the path to a file containing some utility functions. You should use the one supplied, pdclib.php. It's also located at the top level of aBlog2 (./pdcllib.php).|
|URL to the Extjs library||This must be an absolute URL such as /extjs-3.0.3. |
|URL to the Xajax llibrary||This must be an absolute URL such as /xajax_0.5. |
|Path to the image directory||The path to where files that are uploaded will be stored. It must be writable by the web server. The program will create this directory if necessary. It will create subdirectories for every user who uploads a file. Normally this would go inside the applications directory. By default it uses an /images subdirectory or your application.|
|Database Server1 ||The name of the database server you'll use.|
|Database User1||The name of the database user account which has write access to the database.|
|Database Password1||The password for the database user account.|
|Database Name1||The name of the database that you're going to use of the database. The user you entered must have write access to this database.|
|Table Prefix1||Some text that will be appended to database tables. By changing the prefix you can have multiple copies of aBlog use the same database. Limited to 10 characters.|
1 Depending on how you are handling the database, these fields may or may not be needed.
2 If you are using aLogin or anything else that uses the same database and utility libraries, they should all use the same copy. For example, you could point these fields to the copies of mysql_datalib.php and pdclib.php that live in the aLogin directory.
3 Single and double quotes in text strings need to be double escaped. For instance, an application name of Paul's site would need to entered as Paul\\\'s site. These strings are processed twice. The first pass would result in Paul\'s Site and the final path would give Paul's Site.
Paths can be given either in absolute terms or relative to the aBlog main directory. Paths are not URLs. For instance, if your web servers data tree starts at /var/www/html and your application lives in the directory myApp at the top level of of the server, and the aBlog2 library lives in the directory aBlog2 also at the top level, the path to the application could be give as either /var/www/html/myApp or ../myApp. The URL /myApp wouldn't work.
Where URLs are asked for you don't need the "http://servername" part of a full URL.