Install Method
There are three methods for installing DOMBlogger:
- Tarball
- RPM Package
- Debian Package
Regardless of which method you choose, make sure you have the prerequisite applications installed and working first.
Tarball
Content to come
RPM Package
Content to come
Debian Package
Content to come
Database Setup
DOMBlogger is written to be relatively database independent. The initial database setup will depend upon which database you choose to use.
MySQL Setup
PostgreSQL Setup
Preliminary Setup
DOMBlogger has a web based configuration. However, before we can successfully utilize that, a few additional steps need to be taken.
Path Configuration
Inside the web directory is a file called
paths.inc.php. You will need to edit this file. The
contents will look something like this:
paths.inc.php$apc_prefix = ''; $configfile = '/path/to/DOMBlogger.config.xml'; $includePath[]='/usr/share/DOMBlogger/include'; $includePath[]='/usr/share/pear'; // do not edit below here $inipath = $includePath[0]; for ($i=1;$i<sizeof($includePath);$i++) { $inipath .= ':' . $includePath[$i]; } ini_set('include_path',$inipath); require_once('common_funcs.inc.php');
Optionally set $apc_prefix to whatever prefix you
wish APC cached entries from the web application to have. If you do
not set it, it defaults to dblog.
Set $configfile to the full path of your
configuration file.
The first item of the array $includePath should be
set the full path of the include directory in the DOMBlogger
installation. The second item of the array should be the full path
to the pear installation on your system.
If you need to define additional directories to the include path for your own php code, you can do that here as well.
Database Configuration
Open the DOMBlogger.config.xml file with a text
editor. At the very top of the file you will see the following:
DOMBlogger.config.xml<mdb2 phptype="mysql"> <username value="dbuser" /> <password value="dbpass" /> <hostspec value="localhost" /> <database value="dbname" /> <prefix value="domblog_" /> </mdb2>
If you are not using MySQL, change the phptype
attribute of the mdb2 node to the database you are
using.
Replace dbuser with your database user. Replace
dbpass with the password for the database user. If
your database is not running on the same machine as the web server,
replace localhost with the host for the database. If
you are using a prefix other than domblog_ for the
DOMBlogger table names, replace domblog_ with your
chosen prefix.
Permissions
Configuration Directory
The web server needs to have write permission to the directory
containing the DOMBlogger.config.xml file, and the
file itself, so that the administrative tools can modify the
configuration. You need to know the user the web server runs as so
that you can grant that permission. For example, if you are using
RHEL or CentOS, the web server user is apache and
group is apache. Use the following command to give
apache user and group the proper permissions:
cd /usr/local/share/DOMBlogger chown -R apache:apache config
Of course, replace /usr/local/share/DOMBlogger with
the path on your system.
Site Directory
There are several directories in the web directory you potentially need to give the web server permission to:
- site/xml
- site/css
- site/js
- site/images
- site/media
You can do it all at once with the following command:
pushd /usr/local/share/DOMBlogger/www/site
chown -R apache:apache {xml,css,js,php,images,media}
However, you may not want to do that. You should only give the web server permission to write to directories it needs to write to.
For example, if you do not plan on working with raw
XML content files through the DOMBlogger interface,
there is no need for the web server to have write permission to
that directory. For more information, see the documentation on
content dirs.