Package Management

QUIQQER installations are extended through Composer packages. Operators install, inspect, update, and remove packages from the installation root.

There are two command-line paths:

• ./console package / ./console --tool=quiqqer:package for QUIQQER package management.
• ./console composer to pass commands directly to the Composer integrated in QUIQQER.

Use the QUIQQER package command for normal package operations. Use direct Composer access when you explicitly need Composer behavior such as require, remove, update, or diagnostic Composer commands.

Inspect Packages

List installed packages:

./console package --list

Show package information:

./console package --show=vendor/package

Search for available packages:

./console package --search=package-name

The available package list depends on configured package sources and update servers.

Install A Package

Install a package through QUIQQER package management:

./console package --install=vendor/package

The package command checks whether the package is already installed and then uses the package manager to require the package.

QUIQQER registers Composer events for package changes. Required setup and cache steps are executed automatically during the package operation. Check the command output for errors before returning the system to normal operation.

Run Package Setup

Run setup for one package:

./console package --setup=vendor/package

Use this when a package-specific setup needs to be repeated without running the full system setup.

Remove A Package

Remove a package through package management:

./console package --remove=vendor/package

--purge is also available. Check the command help on the target installation before removing packages from production systems.

QUIQQER handles required setup and cache steps through its Composer integration. Check the frontend, administration interface, and logs afterwards.

Integrated Composer

QUIQQER has Composer integrated. The console command:

./console composer <composer-command>

passes all following arguments directly to Composer.

Examples:

./console composer require vendor/package
./console composer remove vendor/package
./console composer update vendor/package
./console composer show vendor/package

Use this carefully. It runs Composer directly through the QUIQQER console, including QUIQQER's Composer events for setup and cache handling. It should only be used by operators who understand the package change being made.

Production Checklist

Before installing, updating, or removing packages in production:

• create a database backup
• create a file backup of the installation and runtime data
• check the package name and version constraint
• check package dependencies and compatibility
• schedule a maintenance window when the change affects public behavior
• check that the automatic setup and cache steps completed successfully
• verify frontend, administration interface, and logs