Intranet File Structure - PHP

This article is the second part of a series on intranet application frameworks. Now that we know what the application framework is all about and how it is going to work in an intranet environment, we are going to look at the overall structure and design of the intranet and the applications. Keep reading to see how this will be done.

TABLE OF CONTENTS:

By: Chris Neeman

Poor Best

Rating:

/ 6

July 25, 2007

print this article

SEARCH DEV SHED

TOOLS YOU CAN USE

All applications that are going to be used on this intranet must adhere to the following rules:

They must all have a configuration file that contains application specific data such as the name of the application and database access credentials:

$appname="appname";
$dbsupport =FALSE or TRUE;
//db connection details
$dbtype = 'mysql';
$dbhost = 'localhost';
$dbname = '';
$dbusername = 'root';
$dbpass = '';
$dbpath = "$dbtype://$dbuser:$dbpass@$dbhost/$dbname";
$requires_db_access=TRUE;

All applications must be object oriented in nature. This is not as much a rule as an optional requirement. An application does not have to be object oriented, but for the sake of consistency, if nothing else, I would suggest that it is written in object oriented code.

The file structure itself is very simple. Each application is going to have only one page which will take input and show output. How exactly a given application will function will be shown when we actually create the applications later on. The overall intranet file structure will look like this: