The technical side of the Neos release process is a wild mixture of automated and manual tasks. Some areas are properly documented and some are just known to the elders of the tribe. In fact, I was probably the one, who has a broad overview of the process and tools… until this week.

For Neos 4.0 and Flow 5.0 quite some changes were made under the hood. But even though there's a review process in place and changes are usually well tested by members of the Neos Team and the community, a couple of glitches slipped through. This kept everyone from using the new releases right away in a professional hosting environment using Redis …

A smooth migration path

When working on the fulltext indexing for the Elasticsearch integration for Neos I recently needed a way to debug what was going on inside a Groovy script we use. It's relatively simple, if you know how…

As soon as such a need arises, finding the solution with a quick internet search yields a quick result along these lines:

import  org.elasticsearch.common.logging.*;
ESLogger logger=ESLoggerFactory.getLogger('some.identifier'); 
logger.info('Ah, a log message!');