Installation & Upgrades

Configure a web server for publishing

While there are a few different options for publishing content to a web server (as described in Transports), the most common method is to utilize FTP, FTPS, or SFTP. In order to publish from Cascade CMS to a server using one of these protocols, we recommend following the general steps below (we'll use SFTP as an example, but the steps are similar for FTP and FTPS as well):

Install an SFTP server on the web server
Create an SFTP account for Cascade CMS to use in order to connect and send files
Configure the SFTP account's home directory to something appropriate (in most cases, this will be your web root)
Ensure that the SFTP account has full permissions to the account's home directory and all of its subfolders (this is necessary so that the CMS can create, update, and remove files from the website)
Configure the firewall to allow traffic from the Cascade CMS server over port 22

Note: Port 22 is the default for SFTP, but if you are listening on a non-standard port, you'd want to make sure that you allow traffic over that port for Cascade CMS to connect. If using FTP or FTPS, you would typically need to make exceptions for port 21 or 990 respectively.

Once the SFTP server has been configured as described above, you'll want to verify that you can connect to it from the application server (where Cascade CMS is installed).

We recommend using a 3rd party SFTP client (like WinSCP or Filezilla, for example) for this purpose as it will also allow for you to verify that connecting with the account places you in the expected directory on the web server's filesystem (the home directory of the SFTP account).

After verifying that you can successfully connect using a 3rd party client:

Log into Cascade CMS and switch into the Site you wish to publish
Create a new Transport using the SFTP account credentials that were verified above
Create a new Destination and when configuring it, select the Transport that was created in the step prior to this

The combination of the Transport and Destination are what determine how and where the CMS will publish. More information on that can be found in Determining Where Assets Will Be Published.

Tip: You can run general connectivity tests for both Transports and Destinations by clicking More -> Test Connectivity while viewing them. When testing Destinations, you can optionally choose to send 'dummy' files of 100kb or 1000kb in size. These tests can help to quickly determine if there is some sort of problem when the system attempts to connect using the information provided in the Transport/Destination (related to authentication or firewalls, for example).

Related Links