The web based portion of RingMaster is called RingMaster Server. It this side of RIngmaster that provides multiauthor features.
The Frontier interface to RingMaster assumes the person at the computer is the SuperUser and there is no restriction to the changes that can be made with that interface. In contrast, the web interface allows or assigning different users different levels of access to website projects.
The RingMaster server allows properties of the RIngMaster framework to be changed with the same HTML interface that is used in the local interaction.
RingMaster server offers lots of multiuser collaborative features for the management of content. The RingMaster server acts as a library for the source files of your website project. It arbitrates who has custody of a given file at a time. It does this by letting a user check out and check in a file if they have permission to. Only one user can check out a given file at a time preventing people from stepping on each others changes.
Ringmaster server also provides options for versioning of content, allowing you to track a history of changes made.
The Ringmaster server runs as a set of CGIs. The RingMaster server may be a production webserver, but more often is a internal server on the intranet. The Ringmaster server then publishes content to the production destination. It is often convenient to set up an internal machine as both the Ringmaster server and the staging destination for your website projects.
Table of Contents -- Prev -- Next