Console

QUIQQER installations provide a ./console entry point in the installation root. Operators use it for maintenance, updates, setup runs, cache cleanup, cron processing, backups, and diagnostics.

Run console commands from the QUIQQER installation root:

./console --help

The help output lists the available system tools, package tools, and command groups for the current installation. The exact list depends on the installed packages.

Calling Commands

QUIQQER supports short system tools and named package tools.

Common system tools can be called directly:

./console setup
./console update
./console clear-cache

Use --tool for tools that do not have a short system alias:

./console --tool=quiqqer:health
./console --tool=quiqqer:backup
./console --tool=quiqqer:maintenance --status=on

Package tools are usually called by their command name:

./console package:cron

Use the help output of the installation to see which package commands are available.

Useful Operator Commands

Command	Purpose
./console --help	Show console help and available tools.
./console --listtools	List tools, including tools that require login.
./console --tool=quiqqer:info	Print system information.
./console --tool=quiqqer:health	Run system health checks.
./console package --list	List installed packages.
./console package --install=vendor/package	Install a package through QUIQQER package management.
./console composer require vendor/package	Pass require vendor/package to the Composer integrated in QUIQQER.
./console update --check	Check for package updates.
./console update	Run system and package updates.
./console setup	Run the setup workflow.
./console clear-cache	Clear the QUIQQER cache.
./console clear-all-quiqqer-cache	Clear cache, temporary data, sessions, locks, and QUIQQER cache data.
./console cron	Execute cron processing.
./console --tool=quiqqer:backup	Create a system backup.
./console htaccess	Generate the Apache .htaccess file.
./console --tool=quiqqer:nginx	Generate the NGINX configuration file.
./console --tool=quiqqer:maintenance --status=on	Enable maintenance mode.
./console --tool=quiqqer:maintenance --status=off	Disable maintenance mode.

See Configuration for the configuration files and settings affected by operational changes.

See Package Management for package installation and direct Composer access.

Update Workflow

A typical production update uses this sequence:

./console --tool=quiqqer:maintenance --status=on
./console update --check
./console update
./console setup
./console clear-cache
./console --tool=quiqqer:maintenance --status=off

Prepare backups before running the update. After the update, check the frontend, the administration interface, and logs.

Cron Processing

Cron processing can be executed through the console:

./console cron

Packages can also provide their own cron-related commands. Use ./console --help on the target installation to see the installed cron tools.

Package Commands

Installed packages can register additional console commands. These commands are part of the installed system and can differ between projects.

Use package commands for package-specific maintenance tasks such as imports, queue processing, cache generation, or repair tasks. Check command help before running destructive or long-running operations.

Use Package Management when installing, removing, or inspecting installed packages.

Safety Rules

• run commands from the installation root
• use the same PHP version as the web runtime when possible
• run production updates inside a maintenance window
• create backups before updates, migrations, or destructive commands
• check the command output and logs before running follow-up repair steps
• do not run package-specific commands from another project without checking their help output