Goals

The aim of this document is to introduce you the basics on how Copix organize your application.

Only one entry point

As you may already have noticed, Copix uses only one entry point for your applicataions: index.php?.

Ths file is the one and only PHP file that you must let public for user (in the publication directory of your web server). Other files don't need to be published, Copix will automatically includ them.

The advantage of this system is that you don't need to bother about what could happen if a malicious user wants to include another file, because they are simply unreachable!

This entry point includes a set of configuration files (mainly copix.inc.php)

and instanciates the ProjectController? which will be in charge, through its "process" method, to launch the application.

From this moment on, Copix takes control and transfers the request to objects able to handle it.

A word about modules

If we super-simplified the role of Copix, we could say that it attemps to get a set of modules to work. These modules being developped according a common model, to work.

What's called a module in Copix is a set of files (classes, templates, actions, resources) acting in order to get a fonction (forum, blog, news, search engine an so on).

The translation of the page is still under process....