To use Xamboo
as your CMS dev framework, you will need:
- A webserver (Apache, nginx, etc.)
- PHP 5.3 minimum, PHP 7 recommended
Always download the latest version from github https://github.com/webability/xamboo
You will get a file with the format: xamboo-xx-yy-zz.tar.gz
Where xx-yy-zz is the current version of the framework.
1. Linux installation
You must unzip the file xamboo-xx-yy-zz.tar.gz where you want to install the Xamboo.
When decompressing, it will creates a 'xamboo' folder with all the code inside.
This folder should not
be in a public directory accessible by Web, either internet or localNote: It is recommended to put the code xamboo is a directory one level above the same web site, or in a directory accessible by the web site.
In your linux server with an Apache, you generally have a base directory website:
Unzip xamboo in /var and you obtain:
Within xamboo, there is a folder called "site".
You can link this folder to the root of the website, or use any other folder as you like, and copy the files present here in the root folder of you website directory.
2. Installing the wrapper
.htaccess files in the public folder you linked with yout webserver:
They are in [?]/xamboo/site
At the beginning of the file, there are 3 directories that link Xamboo settings.
Change directories to link the system xamboo folder where you have installed.
By default, it will searches xamboo as the first parent directory of the website root dir.
index.php is and example and can be modified to what is required for the proper functioning of your site (eg user login, logs hits, configuration and directories from files, database connection, etc .)
.htaccess** file works the same way, it defines the rules to make the apache wraps to the index.
You can make an access file equivalent for other web servers if you do not use apache.
Please read below in the chapter "Reference - Wrapper" for the minimum requirements to run Xamboo and how to use it.
3. Installing the maintenance file
Copy maintenance.html file in the public folder of the web
This in xamboo / site
This file is used when the system switchea to "Care Instructions" from the configuration mode. You can specify any file, by default it is this.
4. Install the base system
Within the xamboo / site directory, then comes a file Base.lib
This file contains its own Base file, Base_engine derivative of Xamboo in which you can add all the functionality you need for your own site.
You can leave the library at the root of your site (where you copied index.php) or protect inside a folder includes its own classes.
What is important is that the system has access to it.
5. Example of installation
5.1 Very Basic Installation
/ Var / xamboo Base Installation
/ Var / xamboo / include PHP Libraries
/ Var / xamboo / site Root Web Site
/ Var / xamboo / repository data repository site
5.2 Advanced installation
The tool follows Installs in /home/sites/mi-sitio.com:
/home/sites/mi-sitio.com Base Installation
Root /home/sites/mi-sitio.com/site website
PHP Libraries generally /home/sites/mi-sitio.com/include
Libraries /home/sites/mi-sitio.com/include/base own site, put here the Base.lib
Libraries /home/sites/mi-sitio.com/include/core the core (comes with Xamboo)
Libraries /home/sites/mi-sitio.com/include/datasources the engine Xamboo
Libraries /home/sites/mi-sitio.com/include/entities Singletones (access to databases, utilities, etc.)
/home/sites/mi-sitio.com/include/pages Pages website
Libraries /home/sites/mi-sitio.com/include/patterns the engine Xamboo
Libraries /home/sites/mi-sitio.com/include/throwables the engine Xamboo
Libraries /home/sites/mi-sitio.com/include/xamboo the engine Xamboo
/home/sites/mi-sitio.com/include/__autoload.inc Autoload of several directories include (Comes with Xamboo amended to add all necessary folders)
/home/sites/mi-sitio.com/repository data repository acplicación
You can locate pages within data repository or within the include, to suit the webmaster. The advantage of having them in the include is to backup all code beyond data that may be within the repository, which are usually bigger in size, but longer life cycle (images, caches, documents, etc)