Select a site

IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.

Deployment

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. 

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.

Cloud deployment

Azure Web Apps and Azure Cloud Services 

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.

Amazon Web 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.
This section contains:
  • Deploy projects to shared hosting
    Use this procedure to migrate existing Sitefinity CMS project from your development machine to a shared hosting using an FTP connection.
  • Deploy projects to virtual private server
    Use this procedure to migrate existing Sitefinity CMS project to a virtual server to which you have full access.
  • Deploy projects to Azure Cloud Services
    Migrate your Sitefinity CMS project to Windows Azure cloud services.
  • Deploy projects to Azure Web Apps
    Use this procedure to migrate your project to Azure Web Apps. The platform is designed for developers and provides them with the ability to develop web, mobile, and integrated scenarios in their preferred language, framework, and IDE. Azure Web Apps takes care of the security, scalability, and staging infrastructure and offers a fast and easy deployment.
  • Deploy projects to Amazon Web Services
    Use this procedure to run your project on Amazon Web Services and to configure additional storage and search services. Amazon Web Services is a cloud computing platform that has a rich set of services, which you can use to run Sitefinity CMS without the need to manage your infrastructure.
  • Best practices: Hosting, deployment, NLB

Back To Top

Next: Upgrade projects in Continuous delivery