You can deploy websites via deployment packages. This means that when a project is exported for deployment, the sites that were created will also be exported and deployed to the next environment. To do this, you need to mark the site to be configured by deployment.
EXAMPLE: On the Development environment you create a website and configure its modules. If you mark the site for deployment, it will be exported together with the deployment package and when the package is uploaded to the next environment, the site will be created there with the way you have set it up on the Development environment.
NOTE: When a site is marked for deployment, you cannot configure it on the next environments where it is uploaded. Settings, such as modules, providers, site languages, online or offline mode will be inactive.
Mark a site for deployment
NOTE: The restrictions are only in the UI, you will still be able to modify the site using the web services or the API. However, the next import will override the manual changes made to the site.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important