ShippedSymfony hosting
on Shipped.
Keep your Symfony services, controllers, and components. Deploy the application with the runtime and supporting services it needs to do its work.
Build for the production environment
Package your Symfony application with its Composer dependencies, required PHP extensions, and server configuration. Make environment settings explicit and supply private values through secrets. Shipped runs the web service while your project controls its public entry point, compiled assets, and application-specific build steps.
Move message handling out of requests
If your application uses Symfony Messenger for asynchronous work, deploy its consumer as a separate worker. Choose the transport your application supports and connect its durable backend. That gives imports, notifications, and other message-driven tasks their own process rather than tying their execution to a browser request.
Keep releases and data changes understandable
Use staging to check service configuration, message handling, and database changes together. Publish through GitHub or your coding agent, then inspect logs when a command or request fails. Plan migrations alongside deployment history so you understand which application releases remain compatible with the current database schema.
A little more detail
Questions about Symfony?
Can I host a Symfony Messenger worker?
Yes. Deploy the consumer with its own start command and the transport configuration your application uses. Durable transport state should live outside the worker process.
Where should Symfony environment secrets go?
Supply private deployment values through Shipped secrets and load them using the configuration approach your project supports. Keep production credentials out of committed source and browser assets.
From your workspace to the web