This seems like a good time to tell you of a new feature going to be released early this year, the PureCM Deployment Service. We are always committed to not just looking after your files but also making your daily work flow easier. The deployment service will be a new stand alone service which you can run to automatically transfer files as changes are made over FTP/SFTP to a server of your choice.
Why use it?
This has been designed to enable you to keep your files up to date on a remote server without having to install PureCM on that machine. One practical example of this is keeping a website up to date on your web server.
The PureCM Deployment Service works by listening for changes in your streams using the PureCM Dot Net Client interface and then copying those changes over to the relevant servers. This takes the hassle of keeping your web server up to date away from you, while drastically speeding up the process by only copying the files that have changed. Any changed or added files are sent to the remote location, while file deletes are removed.
How to use it!
The deployment service comes with its own installer and is configured by a simple XML file, which allows you to set up multiple links between different streams and different FTP locations for full flexibility.
|
<PureCM>
<connection>
<server>localhost</server>
<port>2010</port>
<username>LeadDeveloper1</username>
<password>secret</password>
</connection>
<links>
<link>
<repository>Example</repository>
<stream>Development/Main</stream>
<workspace_path>c:/Deployment/Development/Main</workspace_path>
<ftp_name>SERVER_NAME</ftp_name>
<ftp_type>sftp</ftp_type>
<ftp_path>Development/Main</ftp_path>
<ftp_port>22</ftp_port>
<ftp_username>admin</ftp_username>
<ftp_password>secret</ftp_password>
</link>
</links>
</PureCM>
|
The PureCM Deployment Service requires a machine set up with the PureCM client installed and enough space to create workspaces for each of the streams you wish to FTP. This does not have to be on the same machine as the PureCM service.