Cinnamon 3.6 Server VM and Client

The newest version of the Cinnamon Enterprise CMS is finished: Cinnamon 3.6

New features

  • Microservice-Change-Trigger: You can configure almost all API requests with a pre- or post-trigger which calls a remote web service with all the parameters available to the server at the respective stage. 
    Possible applications:
    • Blocking of API requests. If the remote service sends a non-OK response at the beginning of a request, the Cinnamon API call will not be executed. Use case: validity checks on documents through third party tools (no need to add Grails plugins to Cinnamon, use any language / tool you want to implement custom features).
    • Enhancement / modification of parameters. Example use case: ensure that all documents have a valid copyright header - if one is missing, add it prior to storing the content in the repository.
    • Trigger render server and other tools: if new content is stored or existing content is updated, you can now start a render server process to generate updated renditions of the content (for example, running a DITA to PDF conversion process which also creates thumbnail images [some customization required])
    • Logging of Cinnamon responses to third party tools / services.
  • Summary-flag: Many parts of the API have been enhanced to accept summary information on content. This way you can use the client application to easily searchable meta data which can be displayed without fetching the complete content of a document or data item.
  • Flag to disable change tracking for system accounts: normally all changes to an object are tracked and the modified date field is updated as well as the modifier data. This caused system accounts (for example the render server) to appear as modifiers on documents where they just updated meta data (thumbnails etc). But when looking at a document, most users want to track human interaction with the content, not modifications by system users. Cinnamon 3.6 allows you to enable / disable this.

Updates

Incompatible Changes

Cinnamon server now uses one repository per installation. Handling multi-database multi-tenancy on each request was more trouble than it was worth, and it was never really used by customers.

Download

  • Demo Server VM 3.6.1 (4.7 GByte, includes DITA sample data)
    md5sum: f4c4de6d9ac5bfd21639fe3e01873840
    sha512sum:
    945f55294c3cafd0f8b32241a0967e0d05b0d70ce2cf6ee \
    4e2b8768bb18db9f66055025b6e4df66ad02ed279833e6fd8cb26f876 \
    28c7d73230a4da239ce09b50

  • Desktop Client (500 KByte)
    md5sum: c01f77e3ee8f15b12b91e41efc6d5fc3
    sha512sum: 
    bfe340e9c4f4609046eba60c2d20e13cb5d9dcde45a95 \
    6ad8cef7f21c50ce0ab15b411dc94c0edc4b8743ed870d4e9611 \
    9ec7adbd6b23b75121aa1f3545df836
  • Introductory video for the very first steps once you have downloaded both client and server

The source code for the server and its dependencies is available from the Github repositories:

The source code for the client is available via SourceForge.

The Cinnamon homepage can be found at: http://cinnamon-cms.com

 

Edit: updated link to new version 3.6.1 (bugfixes, more sample data)