AI-Assisted Installation

QUIQQER provides an installation skill for AI clients that can guide an operator through the official installer step by step:

• QUIQQER Install Skill

Use this skill when an AI client should assist with a new QUIQQER installation on a server or local development machine. The skill is not a replacement for the official installation guide; it defines how the AI client should prepare, explain, confirm, run, and verify the installation steps.

When To Use It

Use the installation skill for guided installation sessions where the AI client has terminal access and the operator wants interactive help.

Typical use cases:

• preparing a new QUIQQER installation directory
• checking whether PHP and a download tool are available
• downloading the official installer PHAR
• starting the interactive installer
• explaining installer prompts before the operator chooses values
• stopping on errors and proposing the next recovery command

For the general installation flow, start with the Installation page.

Safety Model

The skill is designed for system-changing work. The AI client should:

• show each command before running it
• ask for confirmation before every command that changes the system
• stop immediately when a command fails
• explain the failed command, likely cause, and next recovery command
• avoid destructive commands unless the operator explicitly approves them
• avoid exposing passwords, tokens, or other secrets in chat output

This confirmation model is especially important on production servers and shared development machines.

Default Installation Flow

The guided flow uses the official installer:

wget https://update.quiqqer.com/quiqqer-installer.phar
php quiqqer-installer.phar install

If wget is not available, the skill can use curl instead:

curl -L -o quiqqer-installer.phar https://update.quiqqer.com/quiqqer-installer.phar

During the interactive installer session, the AI client should explain each prompt briefly, recommend a sensible default where possible, and wait for the operator's decision.

Non-Interactive Runs

Non-interactive installation should only be used when the operator explicitly requests it and all required values are known.

Before running a non-interactive command, the AI client should collect the target directory, database values, administrator values, host, project, language, template, required packages, and development mode choice as needed. It should then show the complete command and ask for final confirmation.

Completion Checklist

At the end of a guided installation, the AI client should report:

• whether the installation completed successfully
• the installation path
• selected host and project values
• any values that still need operator action
• the next step for logging in or completing setup

If the session is interrupted, the AI client should determine the last completed step and ask whether to continue from there.