You use the following deployment procedures to migrate a Sitefinity CMS project from your development machine to a production server. After the physical relocation of the application, all CMS functionality continues to operate. You do not need to install Sitefinity CMS on the server. You must only move the files of the project to the production server.
IMPORTANT: To successfully deploy Sitefinity CMS, your hosting provider must support .NET 4.5 Framework and Full trust. You can find a list of Sitefinity’s official hosting partners on http://www.sitefinity.com/partners/hosting-partners.aspx.
The following screenshot is an example of your project files:
The files are located in your Projects folder.
For more information about managing your project files, see Administration: File and folder management.
For more information, see Administration: Configure the application restart behavior during uploads.
You can deploy your Sitefinity CMS projects to Azure Web Apps and Azure Cloud Services.
Azure Web Apps has faster deployment and is easier to use. It is more suitable for less complex projects that need to be delivered fast. If your project is more complex, for example it requires background processing or internal communication, it is more suitable to use Azure Web Services that requires more time to setup and deploy, but provides a better infrastructure.
For a comprehensive comparison between the two services, see Azure Websites vs Cloud Services.
You can also deploy your project to Amazon Web Services that has a rich set of services, which you can use to run Sitefinity CMS without the need to manage your infrastructure.
NOTE: Because the configuration files, generated by the Analytics module, are from a different provider, they cannot be stored in the database. Therefore, you cannot configure the module after you deploy the site in the cloud. You must do it before the deployment and the files need to be included in the deployment package.
Back To Top