---
title: "Incremental deployment"
manual: "TYPO3 Explained"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3coreapi:manual-deployment-incremental@main"
source: "Administration/Deployment/IncrementalDeployment/Index.rst"
modified: "2026-09-15T12:49:12+00:00"
---

# Incremental deployment

After the initial deployment, incremental deployments are used to update code and
configuration.

Steps:

## Prepare the updated version locally:

-   Apply code or configuration changes
-   Run:

    ```bash
    composer install --no-dev
    ```

## Transfer only updated files to the server

Include:

-   `public/` (excluding `fileadmin/`, `uploads/`)
-   `config/`
-   `vendor/`
-   `composer.lock`
-   etc.

Do not include dynamic or environment-specific files such as:

-   `var/`, `public/fileadmin/`, (these are managed on the server)

You can speed up the transfer using archive tools like zip or tar, or use
[rsync](https://docs.typo3.org/permalink/t3coreapi:deployment-rsync@main)
to copy only changed files.

## If database changes are required:

-   Run the Upgrade Wizard in the TYPO3 backend
-   Or apply schema changes via CLI tools

## Flush TYPO3 caches:

```bash
./vendor/bin/typo3 cache:flush
```

> [!NOTE]
> Use a deployment script or tool such as
> [rsync](https://docs.typo3.org/permalink/t3coreapi:deployment-rsync@main) or
> [Deployer](https://docs.typo3.org/permalink/t3coreapi:deployment-deployer@main)
> to automate incremental deployments and avoid overwriting persistent data.