Created: Friday, 04 November 2016 16:53
Last Updated: Friday, 04 November 2016 17:36
Written by Ingo
The Cinnamon Portable Edition is a way to run a full version of Cinnamon on your Windows desktop without installing any software or configuring your environment in any way.
The current version for download at the Cinnamon's SourceForge.net project page is really outdated, so I have put together a new version. It's a little rough on the edges and does not include a DITA renderer at the moment, but it has all the features of the most recent Cinnamon version.
Download the zip archive of Cinnamon Portable 3.7, use right-click to set the is-secure flag on the properties page (otherwise Windows holds all contained code as suspicious and you cannot run the programs). Then unpack the archive and read the Getting-Started.html page.
Note: the server's background Java process tends to stick around even after termination. You may need to end it via the task-manager.
Cinnamon Portable 3.7 Preview edition checksums (to verify the integrity of your downloaded files):
sha256sum: 77de5c153ad34b78c0d044a68a9efd \ b227afbee173a39625c95b429c8ef263b5
Created: Tuesday, 28 June 2016 22:12
Last Updated: Thursday, 03 November 2016 17:18
Written by Ingo
The newest version of the Cinnamon Enterprise CMS is finished: Cinnamon 3.6
- 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.
- 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.
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.
- Demo Server VM 3.6.1 (4.7 GByte, includes DITA sample data)
- Desktop Client (500 KByte)
sha512sum: bfe340e9c4f4609046eba60c2d20e13cb5d9dcde45a95 \
- 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)
Created: Saturday, 30 April 2016 07:06
Last Updated: Saturday, 30 April 2016 07:06
Written by Ingo
Exception in thread "main"
org.apache.hadoop.security.AccessControlException: Permission denied:
user=publisher, access=EXECUTE, inode="/data/foo/configuration.xml":publisher:publisher:-rw-r--r--
Always a nice error message to waste some time upon - your HDFS user seems to have all the required permissions, the file exists, and still you get the a Permission denied.
In this case, the EXECUTE permission seems to be missing, but that's surely bogus, since you only want to read a single file, not execute it.
Turns out, when accessing a file as a folder, HDFS checks the permission and denies further access because the file cannot be used as a folder. In this case, the code was searching for
/data/foo/configuration.xml/foo/configuration.xml due to a two pieces of code both appending a part of the path to the final filename.
Created: Tuesday, 06 October 2015 21:03
Last Updated: Tuesday, 06 October 2015 21:03
Written by Ingo
This posts contains links to further Hadoop resources.
Dewarim.com download area - contains:
- Hadoop 2.7.1 compiled for Raspberry Pi 2 B
- Image of the Hadoop master node for Raspberry.
Learning Hadoop - my Github repository with code examples