Deploy to production
You have successfully created, configured, and updated your project in Kentico SaaS. So far, we have only discussed the QA environment. Now let’s finally deploy your solution into PROD in Xperience portal.
Note that the deployment environments are not intended to replace staging.
The QA and UAT environments and the deployment packages are intended to ensure all the functionality, features, and key branding assets (e.g., logos) are present in your SaaS application. The editors should prepare content in the PROD environment.
See our documentation for information about deployment best practices.
Deploy from QA to PROD
Currently there is no option to upload a deployment package directly to the PROD environment in the Xperience Portal using the Xperience Portal API currently. The only way to do it is through the QA or UAT, depending on your license tier.
When your solution is ready to move into the production environment, the process is very straightforward.
To start, visit your Xperience Portal and ensure you are working under the correct project.
On the Deployments page, under the QA environment, open the Deploy to dropdown and select PROD (the only option in our example, as we’re using a Level 1 license).
You’ll see a pop-up warning that the application will be temporarily shut down for the duration of the deployment.
Click Start deployment.
Just like in QA before, the portal queues your deployment before changing its status to In progress.
You may not see your queued deployment immediately. If you clicked Start deployment and the system navigated you back to the Deployments page, but you’re not seeing your deployment queued or in progress, do NOT click Deploy to → PROD again. Instead, try waiting for a minute or refreshing the page.
Otherwise, you may end up with several identical deployments queued, unnecessarily taking up resources.
You can watch the status and time elapsed on the Deployments page.
Check your progress
Once the PROD deployment finishes, just like before, you can see it in the Deployment history section with status and other information, and the option to download logs.
In the PROD section of the Dashboard, you can also see the new deployment info and a link to the Xperience Administration in PROD (using the system domain). If you click the link, you should be able to sign into and browse your solution’s administration in the cloud production environment.
During the channels configuration step, we created default channels and domains for all of your environments, so now you should also be able to see your PROD live site through your production website channel default domain:
Set up custom domains - optional
Xperience Portal allows you to set up custom domains for the PROD environment.
System domains
Under Channels and domains → System domains, you can see system domains for all your environments:
- Administration (append /admin to the domain to visit the Xperience administration for the environment)
- Email sending
- Email service
You cannot rename any of these domains, but you can add another domain as an alias for Email sending and Email service in PROD by clicking the green swap icon. If you have an existing valid domain you can use, feel free to give it a shot.
Channel domains
Under Channels and domains → Channels, you can define custom domains for each channel.
For example, click the green globe icon on your Dancing Goat Website channel, click Add domain, and go through the wizard. Notice that the system will only allow you to create a custom domain for PROD.
The dancing-goat.com domain in the video is just imaginary for the sake of a quick demo. It does not have DNS records configured, so its creation will eventually fail.
Similarly, you can set up custom domains for your PROD email channel.
Previous step: Update a QA deployment using Xperience Portal API — Next step: Where to go from here
Completed steps: 6 of 7