Configuration

QUIQQER stores system configuration in the installation's etc/ directory. Many operational settings are also exposed through the administration interface.

Operators should understand both layers:

• etc/ files are the persisted configuration files used by the runtime.
• Administration settings provide a UI for selected configuration values.
• Package settings can add additional configuration areas.

Configuration Files

Common files in etc/ include:

File	Purpose
conf.ini.php	Main system configuration such as paths, host, web server type, database, mail, session, and runtime flags.
cache.ini.php	Cache-related configuration.
plugins.ini.php	Installed package state and package-related metadata.
projects.ini.php	Project registration and project metadata.
templates.ini.php	Template assignment and template-related data.
source.list.ini.php	Package source and update server configuration.
license.ini.php	License-related configuration.
htaccess.custom.php	Custom Apache rules included during .htaccess generation.
nginx/nginx.example.conf	Generated NGINX configuration output.
nginx/conf.d/	NGINX include files for local PHP, SSL, redirect, whitelist, and server customizations.

Do not commit production etc/ files into public repositories. They can contain environment-specific paths, database credentials, salts, license data, mail settings, and hostnames.

Main Configuration Areas

conf.ini.php is grouped into sections. Important operator-facing areas are:

Section	Purpose
globals	Installation paths, host, language, timezone, cache flag, development flag, maintenance flag, and runtime behavior.
db	Database connection.
webserver	Web server type and HTTPS behavior.
mail	Mail transport, queue, sender, and logging settings.
session	Session backend and lifetime.
session_redis	Redis connection for session storage when Redis sessions are enabled.
error	Error reporting and error mail behavior.
smarty	Template engine runtime settings.

Changing these values can affect the whole installation. Keep a backup of the file before manual changes.

Web Server Settings

The webserver section controls which generated routing file QUIQQER expects:

Setting	Use
webserver.type	Selects apache2.4, apache2.2, or nginx.
webserver.forceHttps	Enables generated HTTP-to-HTTPS redirects where supported by the generated server file.

Changing the web server type affects generated routing files. Regenerate the matching file after changing it:

./console htaccess
./console --tool=quiqqer:nginx

See Web Server for Apache and NGINX details.

Session Settings

The session section controls where user sessions are stored. Current Core settings expose filesystem, database, memcached, and Redis session storage.

When Redis is used for sessions, the connection value is stored in session_redis.server. Keep the PHP web runtime and the CLI runtime aligned: both must be able to reach the configured session backend.

Session backend changes can log users out or invalidate active sessions. Plan them during a maintenance window and verify login in the administration interface afterwards.

Administration Settings

The administration interface exposes selected configuration values through settings panels. Core settings are declared by XML files such as:

• packages/quiqqer/core/admin/settings/conf.xml
• packages/quiqqer/core/admin/settings/cache.xml

Installed packages can add their own settings panels. These settings are still stored as system or package configuration and should be treated as operational changes.

Use the administration interface for normal changes when a setting is available there. Manual file edits are useful for recovery, deployment automation, or settings that are not exposed through the UI.

Changing Configuration Safely

Before changing configuration:

• create a backup of the affected etc/ file
• note the old value and the reason for the change
• check whether the setting is available in the administration interface
• understand whether the setting is environment-specific
• plan cache clearing or setup runs if the setting affects runtime behavior

After changing configuration:

• clear relevant caches
• run setup when package configuration or generated definitions changed
• regenerate web server files when web server customizations changed
• verify frontend and administration interface
• inspect logs for configuration-related errors

Examples

Maintenance mode can be controlled through the console:

./console --tool=quiqqer:maintenance --status=on
./console --tool=quiqqer:maintenance --status=off

Apache custom rules should be added to:

etc/htaccess.custom.php

Then regenerate .htaccess:

./console htaccess

Cache behavior can be changed through cache settings in the administration interface or through the corresponding configuration files. Clear caches after changing cache behavior.