5.4 / 2014.11
Use of DFS clustering is a requirement for use in Clustering setup, for overview of clustering feature see Clustering.
What it is meant for
The legacy_dfs_cluster IO metadata handler can be used to store images on NFS, while remaining compatible with legacy, using the DFS Cluster file handler. It stores metadata in the ezdfsfile table from the legacy database. It is meant to be used to write binarydata to a locally mounted NFS server.
Configuration
Note for use with legacy
This handler requires legacy to be configured to use DFS clustering.
Assuming that your database is named ezdfs, configure it, for instance in ezpublish.yml:
Important: take good note of the
$var_dir$/$storage_dir$ part for the NFS path. Legacy expects this path to exist on the NFS mount in order to be able to read and write files.Web server rewrite rules.
The default eZ Publish rewrite rules will let image requests be served directly from disk. With native support, files matching ^/var/([^/]+/)?storage/images(-versioned)?/.* have to be sent to the normal index.php
In any case, this specific rewrite rule must be placed without the ones that "ignore" image files and just let the web server serve the files.
2 Comments
Carlos Revillo
These two rewrite rules should change index.php by app.php, shouldn't they?
Edit: at least since index.php is not present anymore. could be still valid for 5.x though
André Rømcke
Carlos Revillo This is space for eZ Publish 5.x, we made a new one for eZ Platform, check for instance TECHDOC space.