Back to the 1 2 ∞ documentation

Installation instructions for the 1 2 ∞ system

author: Lodewijk Evers

email: lodewijkevers@jadwigo.nl

website: http://www.jadwigo.nl/tools

created: 2004 09 09

modified: 2004 11 08

This document describes the installation and configuration of the be system.

Contents

  1. Requirements
  2. Installation
  3. Database

1. Requirements

A basic LAMP (Linux Apache MySQL PHP) installation will do, but the system works on other PHP/MySQL capable servers too. PHP 4.x is minimum requirement.

2. Installation

To install, first create a database, call it anyway you like, you'll insert that name into the configuration later.

Then insert the data from the sql file into it. (rtm-full.sql is the most probable one.) In be_user you need to add a user and make the password md5() encrypted so you can login. (you can use phpMyAdmin for that)

At last set all the relevant variables in "./be/include/config.inc.php" and make the following directories writeable for the webserver:

If you get an error in the file select or image select popups you probably messed up here.

The rest can be managed from within the system.

3. Database

Special tables are:

be_config = configuration variables that will be globally available. be_config_modules = the backend structure, play with it and you'll see. be_{lang}_* = the labels and messages in a language, where "{lang}" is an identifier that is set in "be_config" with the label "sys_lang".

Special fieldnames:

Any field named "id" has an auto_incement flag and should be used as the primary identification for that table.

Any field that ends in "_id" is a foreign key, they refer to "id" field in the table with the tablename that is most logical, eg. "user_company_id" refers to the "id" field in the table "be_company". This system will automagically use this connection. Take care that if you make new tables that the datatypes for the two fields are compatible.

Any field that ends in "_location" refers to a file that resides in "../data/uploads/{tablename}/{fieldname}". The directory will be created automagically on first use, providing the webserver process has write access to "../data/uploads/". (The location may be set in the "be_config" table with the "dir_data" and the "dir_uploads" variables.)

Inline images are placed in "../images/{tablename}/{fieldname}", similarly to files.

This file is also available in plain text.