Confirm the PHP requirements of the selected Symfony branch, required extensions and database connectivity. Prepare a tested release and an authorised way to run its console commands.

1. Upload the reviewed application and committed Composer lock file to a release directory. Install production dependencies with the selected PHP runtime and omit development packages unless a justified build step needs them.

2. Configure the production environment with debug disabled. Most applications use APP_ENV=prod and APP_DEBUG=0; check any custom runtime bootstrap as well.

3. Point the domain to the public directory. Keep configuration, source code, logs and dependency metadata outside direct web access.

4. Clear and warm the production cache using the application console as the intended deployment account. Apply approved migrations separately and build the assets used by this application.

5. Restart persistent message consumers after the release changes and confirm the supervisor launches them from the new path.

Check a public page, an authenticated request, an asset and a database write. Inspect the private log and verify that debug pages or the development profiler are not publicly exposed.

A cache warmup failure can indicate a missing extension, unresolved environment value or incompatible service definition. Correct the reported cause before switching the active release.

• Using Symfony secrets on a hosting server
• Managing Symfony cache pools after deployment
• Serving Symfony assets from the correct public directory
• Changing a Symfony database schema safely

• Symfony deployment
• Symfony configuration