Installation

This page gets Quiote onto your machine. Quiote is a Composer library, so you add it to a project like any other dependency — there is no separate installer. Work through it in order: check the requirements, install with Composer, then verify the CLI runs. Once it does, Your first application builds something with it.

Requirements

Before installing, make sure your environment has these. The extensions are the ones the kernel needs to boot; the optional table further down lists ones that unlock extra subsystems.

PHP 8.5 or higher
Required extensions: dom, intl, SPL, Reflection, PCRE (and libxml, which dom depends on)
Composer

Optional extensions that unlock additional functionality:

Extension	Enables
`xsl`	Transformation of pre-1.0 style configuration files
`tokenizer`	More efficient config cache generation
`session`	Built-in session handling
`PDO`	PDO-based database connectors
`iconv`	Charset conversion between ISO-8859-1 and UTF-8
`APCu`	APCu-backed config cache for persistent workers

Installing via Composer

Quiote is available on Packagist. The latest stable version is v4.0.0.

Follow these steps from your project directory.

Require the package. In an existing Composer project, one command adds Quiote and pulls in its dependencies:
Terminal window
```
composer require quioteframework/quiote
```
Or add it to composer.json by hand. If you prefer to edit the manifest yourself, add the requirement, then run composer install:
```
{
    "require": {
        "quioteframework/quiote": "^4.0"
    }
}
```
Terminal window
```
composer install
```

Verifying the installation

Confirm the CLI runs. Composer installs the quiote binary to vendor/bin. Ask it for its version — a version string (currently 4.0.0) means Quiote is installed and runnable:
Terminal window
```
vendor/bin/quiote --version
```

See The command-line tool for everything quiote can do — including scaffolding a new application with quiote new.

Next steps

With Quiote installed, build your first application: Your first application walks through a scaffolded app end to end — the front controller, a route, an action, a view, and a template.