Hi,

What do you mean with "Deployment controls is for automated deployment"?

The deployment controller service enables compilation of OutSystems applications and broadcasting of the deployment to multiple front-end-servers. It runs in each environment in one of the servers.

When you click 1-click-publish for a solution, the deployment controller is used, how else would the applications be compiled and broadcasted to all servers?

Regards,

Daniel

An OSP file is a collection of modules, application and extension. You can rename an OSP file to .zip to inspect its contents.

For deployment, two key services run on the OutSystems Platform Server:

1. Deployment Controller Service – This service handles the compilation and broadcasting of applications, as noted by @Daniël Kuhlmann.
2. Deployment Service – This service manages the actual deployment process.

When you upload an OSP file, both steps—compilation and deployment—must be completed.

In a farm environment, all front-end servers run the Deployment Service, while the Controller Server runs both the Deployment Controller Service and the Deployment Service.

Thank you Siya for your respectful and thorough response.  I was unable to verify OSP deployment via controller from OS training or documentation.   In my mind a Lifetime deployment is automated.  Deploying via OSP is not as automated.  Thanks for confirming.

• Deployment controller service: Enables the compilation of OutSystems applications and the automated deployment of the code to multiple servers.