collective.recipe.filestorage does not detect zope parts if zeo-address differs
Basically I'm taking about this bit of code in __init__.py
Unfortunately in my case zeo_address is '0.0.0.0:8100' and part.get(
They do not equal therefore it's never added to the list. Is is necessary to configure zeo to bind to 0.0.0.0:8100 since otherwise the zope clients on seperate cannot connect to it in our Amazon cluster.
I understand this is a bit of an edge case, but technically there is nothing wrong with my buildout.
I have attached a patch for __init__.py that solves my problem and still maintains original functionality