> For the complete documentation index, see [llms.txt](https://docs.cmsfullform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cmsfullform.com/overview/install/using-composer.md).

# Using Composer

Composer is the easiest and fastest way to install the framework, ensuring you always get the latest version with all dependencies.

## Step 1: Check Composer and PHP versions

Before installing, check if **PHP 7.4+** and **Composer** are installed:

```sh
php -v
composer -V
```

If Composer is not installed, download it from [getcomposer.org](https://getcomposer.org/) and follow the installation instructions.

## Step 2: Install the PHPFast Framework

Run the following command to create a new project with the framework:

```sh
composer create-project vendor/php-fast project-root
```

* `vendor/framework-name`: The package name of the framework on Composer.
* `my_project`: The project directory (you can rename it as needed).

Once completed, the framework and all required libraries will be downloaded.

## **Step 3: Start the server**

If you are not using Apache/Nginx, you can start the project using **PHP's built-in server**:

```sh
php -S localhost:8000 -t public
```

Then, open [**http://localhost:8000**](http://localhost:8000) in your browser to check if it's working.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cmsfullform.com/overview/install/using-composer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.