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:
composer install --no-devCopied!
Transfer only updated files to the server
Include:
public/(excludingfileadmin/,uploads/)config/vendor/composer.lock - etc.
Do not include dynamic or environment-specific files such as:
var/,public/, (these are managed on the server)fileadmin/
You can speed up the transfer using archive tools like zip or tar, or use rsync 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:
./vendor/bin/typo3 cache:flush
Copied!
Update the reference index:
./vendor/bin/typo3 referenceindex:update
Copied!
TYPO3 reads relations from the reference index, also in the frontend. Update it whenever a deployment adds, removes, or updates an extension or the TYPO3 Core, as this can change the relations defined in TCA. Updating it after every deployment is recommended. See Update reference index.