flowpack/flowpack.decoupledcontentstore

This is the 2nd generation of a Two-Stack CMS package for Neos.

flowpack.decoupledcontentstore's Issues

Allow parallel content releases for deviating workspaces

Flushing Cache when starting a content release could cause issues

Currently the Redis cache is flushed when a content release is started:

Flowpack.DecoupledContentStore/Classes/ContentReleaseManager.php

Line 62 in 195ef1f

$this->contentCache->flush();

This is not optimal as the content release might start later due to the pipeline configuration and parallel running releases influence each other.
Therefore only the cache entries should be flushed which are somehow related to the started release.

DecoupledContentStore could stay compatible to Neos 7.3 and 8 on the same Version

Hi @Sebobo :)

can you add some hints here how you want to achieve this?

The main idea:
We don't want to have (and maintain) separat branches for Neos 7.3 and 8. Sebastian mentioned, that it is possible (and not tooo much afford) to have both Neos Versions supported.

Main Issue would be the transitive dependency to optimized redis cache backend in 7.3 vs Core redis cache backend in Neos 8.

Thanks + Cheers

Copy of "root" into rendering path "documentRendering" can happen too early

The root rendering path is copied in this package, but "when" this happens is a bit random based on the package loading order. This can causes issues with missing renderers, when another package is loaded after the DecoupledContentStore package and then modifies root.

documentRendering < root

Starting two content releases in the same second causes the pipeline to mix up the configuration

Starting a release via startFullContentRelease creates an identifier based on the current second via the unix timestamp.
F.e. starting a second release for another workspace in the same second by another user can lead to a mixup in the pipeline.

In our case we ended up with a mixture of both configurations for each pipeline run and both succeeded but had the wrong result.

Also only one of the releases shows up in the ContentStore module.

Therefore the release id should be made more unique and checked for a duplicate.

Backend module styling bleeds into Neos UI

The DecoupledContentStore Neos backend module uses mostly Tailwind default styles which currently overpower some Neos UI styles.

Default Neos UI:	When in DecoupledContentStore backend module: