Documentation

Destinations

A destination is a location where Ringmaster puts rendered Web files.

A destination may be of one of two types: local or remote

A local destination is any mountable volume This includes local hard drives, or drives you can mount on your desktop over a network

A remote destination is one that is reached by FTP (File Transfer Protocol) If you provide a username and password for a local destination that is a network volume RingMaster will automatically mount that volume if it is needed.

A destination contains the following information

Type:

Either local or remote

Machine Info:

Name: For local destinations this might be an Appletalk zone and machine name. it is set automatically when you browse to select a folder. For remote destinations it is the IP name (ie www.foo.com) of the remote FTP server. Path: Is the complete path to the directory where you want files put. For local destinations this is most easily set by browsing. For remote destinations it is path relative to your login directory.

User Info:

Username: Username for the destination Password: Password for the destination This information is optional, if not defined in the destination resource you will be prompted for this information at each release event. This information is not needed for local destinations on the user's machine.

URL

The URL to chosen destination. This is used when previewing files. If the destination is local and not a active server, you can choose to use a file:/// scheme.

Each item in a RingMaster site is assigned two destinations

A staging destination and a production destination

The staging destination is often a local drive or test server, this is where you preview content during development or revision.

The production destination is where the 'final draft' goes.

Advanced: a production destination can actually be a list of multiple destinations for use in server farms

Generally the staging and production destination properties are assigned to the whole site. However any folder or file can be assigned its own destination. If a subfolder is assigned its own destination, files are rendered to a path relative to the folder for which the destination is defined.

For example say you have a folder in your site at

mysite/otherFiles/movies/

And you assign a destination to this folder that points to:

http://graphics.mydomain.com

Then a file in the Ringmaster site at mysite/otherFiles/movies/largeFile.mov

is rendered to

http://graphics.mydomain.com/largFile.mov

A destination doesn't have to be an HTTP server, it can be an FTP server.

This lets you manage an FTP site, or graphics server as part of one site.(Esp combined with RM object types that auto encode files)

Table of Contents -- Prev -- Next