Documentation

Requirements

Chevereto has very standard server requirements:

File permissions

Chevereto requires write access in the /content, /images and app/content/languages/cache folders. Since Chevereto runs PHP, the web server (Apache, Nginx, etc.) inherit his permissions to Chevereto so if Apache can't write in a folder then Chevereto won't be able to write on it. Make sure that the web server is in the owner group of your website folders to allow Chevereto to work properly.

Also double check the read/write access to the temp folder (/tmp in Unix/Linux and C:/Windows/Temp in Windows).

Settings file (app/settings.php)

By default, the system will try to create the app/settings.php file which is used to store the database connection details. In some server environments, this file can't be created by Chevereto so you must manually create an empty file named settings.php in the app/ directory. The install process will tell you which contents you should put in this file.

Database privileges

Is recommended that your MySQL user has ALL PRIVILEGES over the target database. In normal production environment Chevereto just needs CRUD (create/read/update/delete) permissions to work properly so you can revoke some permissions but in install or update environment it needs full privileges.

Pretty URLs

This refers to the usage of pretty (or friendly) URLs which is accomplished using server rewriting. Depending on your server you will need to follow the adequate procedure to make it work.

Apache Server

You will need Apache mod_rewrite. By default, Chevereto comes with a .htaccess file that manages the URL rewriting so you only need to upload this file and make sure that mod_rewrite is enabled and working

If you have issues with pretty URLs and Apache try enabling the RewriteBase / directive and make sure that in your virtualhost you have Allow Override All

Nginx server

Use the following directives in your site configuration:

# Image not found replacement
location ~* (jpe?g|png|gif) {
        log_not_found off;
        error_page 404 /content/images/system/default/404.gif;
}

# CORS header (avoids font rendering issues)
location ~ \.(ttf|ttc|otf|eot|woff|woff2|font.css|css|js)$ {
        add_header Access-Control-Allow-Origin "*";
}

# Pretty URLs
location / {
        try_files $uri $uri/ /index.php?$query_string;
}

Other webs ervers

For other webs ervers you should refer to any documentation regarding URL rewriting in your server API.