[Mapbender-dev] motion: change file system layout
nimix at gmx.net
Mon Jul 7 15:25:25 EDT 2008
+1 I like the idea of a more structured filesystem.
Why not add a plugin/ directory which has the same function as the mod
directory but contains all modules the are not shipped with mapbenders
standard installation? This would lead (in theory) to a clear division
between customations and core code. This would be the place where the
<project name>_<module name> modules would be.
Christoph Baudson schrieb:
> As most of Mapbender's recent security issues stem from files being
> unnecessarily in the http folder, I think we should move as many files
> as possible out of that directory. Only files which are really loaded
> via http should remain there.
> I motion to
> - move the PHP classes from /http/classes to /lib (and remove the
> prefix "class_"). We can keep wrappers for the sake of backwards
> compatibility (an old class file would only include a new class file).
> - move the external libraries from /http/extensions to /ext
> - create a folder /mod which holds a folder for each module (example:
> these folders
> in Mapbender 2.6 (est. release date Sep 15, 2008)
> I already have a working experimental version in
> The rest will remain untouched now, but will be moved to the new
> folders later on (there is no need for http/frames, http/html,
> http/include, http/print). I'm not sure how to deal with
> as well? I'm also not sure about /http/sld.
> This approach also helps to
> - isolate modules from the core
> - optimize the core
> - remove deprecated modules
> - exchange modules
> For customizations, we recommended to add a folder /http/x_<project
> name> in the past. This folder could be replaced by folders
> mod/<project name>_<module name>. This would help us to integrate
> modules developed for specific scenarios into the Mapbender generic
> development, and also to update overwhelmingly customized Mapbenders.
> Sustainability is the keyword.
More information about the Mapbender_dev