Setup and configure a publishing server
Publishing servers provide the ability to preview and deploy websites that have been produced in the Contensis. Most common environments use two types of publishing server
Staging / Preview Server - Used for previewing new pages and content on a web server that is not publically available.
Production / Live Server - Usually the public facing server(s) of a live website, only final approved content is published to these servers.
Create a staging site or preview server
- Open up the Management Console and expand Project Overview.
- Press on Publishing Servers.
- Click Create Publishing Server, the Create new Publishing Server dialog will open.
Now you need to fill in the dialog with the following details:
- Web site address - the URL that you would like the preview server to use e.g. http://preview.[domainname].com
- Friendly name – a short identifying name e.g. Preview
- Email host – the email host for integration with SMTP services for sending CMS notifications, e.g. smtp.domainname.com
- Type – Test (used to distinguish between live and test servers)
- Enable as Preview Server – Checked. It's possible to have multiple test servers, however you can only preview to a single server.
- Enable FTP cleaning – Checked. This check box enables a process to run that removes any out of date content, it is recommended that this is turned on in all instances.
Note: any custom files delivered outside the CMS will need to be added either to the FtpCleaner_ExcludedDirectories or FtpCleaner_ExcludedFiles settings within Project Settings to prevent deletion by the FTP cleaner service.
- Database – choose the database connection for delivering any dynamic content, this is covered in more detail in Creating a connection to the CMS database.
- Search table name – a name for the full-text catalog default: SearchContent
- Host – the server host name or IP address of the front-end webserver
- Username – FTP account name
- Password – FTP account password
Advanced FTP settings
- Passive – Checked if a Passive FTP connection is used
- Port – Default 21, can be overridden when required
- Server Type – Default FTP, but can be SFTP, FTPS or FTPES.
- Timeout – Set your timeout to 0 to ensure the connection will not time out whilst publishing.
With all the settings in place, check the Enable publishing to this server checkbox.
Create the production / live server
The production/live server setup is identical to the staging/preview server as described above, with the exception of the following settings:
- Type - this is set to Normal.
- Database - needs to be set to a live database rather than a test database.
It is possible to create an unlimited number of publishing servers for both staging/test and production/live environments but in each environment only one preview server is created e.g. only one publishing server is checked with ‘Enable as Preview Server’.
If the front end site requires database access then there should only be one instance of the publishers that should have Enable data publishing to this server set as true. The other publishers should have the database selected in the dropdown but not have data publishing checked. The FTP details should point to the unique servers with valid credentials.
Was this article helpful?