[mapserver-dev] MapServer 8.0 Config File

[jbo-ads]

Hi,

I answer to the MapCache-related question.

As an Apache module, MapCache needs to register in Apache configuration, 
with a line like:

     MapCacheAlias /mapcache "/path/to/directory/mapcache.xml"

which binds "/mapcache" URL path root to a specific MapCache 
configuration file. Several "MapCacheAlias" directives may be specified 
for multiple MapCache configuration files. There is no default, unless 
"/" is a valid MapCacheAlias (which I didn't checked) and it's okay for 
the http server to deliver only MapCache data.

Jérome.


Le 16/06/2021 à 16:19, Steve Lime a écrit :
> Hi Dan, thanks for the feedback.
> 
>   * A default location is a reasonable idea. I started down this route
>     initially but stopped because I can see folks wanting to use
>     different config files for multiple virtual hosts on the same server
>     - so being explicit seemed ok (and simpler). How does MapCache
>     handle it's config file?
>   * I think the config *must* be mandatory for CGI operations. Trying to
>     support both legacy configuration and a config file is just too
>     messy IMHO. With that, we can certainly set some recommended
>     defaults in the example config file that is provided and setting
>     MS_MAP_NO_PATH to true is fine with me. The code as it sits, does
>     require MS_MAP_PATTERN to be set if full-path values are allowed.
>   * +1
> 
> --Steve
> 
> On Tue, Jun 15, 2021 at 8:07 PM Daniel Morissette 
> <dmorissette at mapgears.com <mailto:dmorissette at mapgears.com>> wrote:
> 
>     Great addition.  A few thoughts/questions:
> 
>     - Perhaps the default behavior if MS_CONFIG_FILE is not set could be to
>     look for the config file in /etc/mapserver.conf or
>     $PREFIX/etc/mapserver.conf ... that would simplify configuration even
>     more and would be the natural place where one would expect to find such
>     a config file on Unix/Linux.  (Not sure about Windows though)
> 
>     - If we're going to introduce such a config file, perhaps we should
>     make
>     it mandatory, and also make MS_MAP_NO_PATH=TRUE the implicit default so
>     that unless you explicitly change MS_MAP_NO_PATH then only mapfiles
>     explicitly listed in the config can be used  (I know I've always been a
>     big fan of backwards compatibility, but this time I think it may be
>     simpler for the users to just deal with a config file that is locked
>     down by default instead of the complicated/legacy environment variables
>     in order to secure a server)
> 
>     - I like Seth's suggestion of being able to set global defaults in the
>     config file that are inherited by the mapfiles and can be overridden
>     locally in each one
> 
> 
>     Daniel
> 
> 
>     On 2021-06-15 13:04, Steve Lime wrote:
>      > Hi all: Just checking on folks thoughts on moving forward with a
>     config
>      > file. There was a bit of discussion back in early April...
>      >
>      > https://github.com/sdlime/mapserver/wiki/MapServer-8.0-Config-File
>      > <https://github.com/sdlime/mapserver/wiki/MapServer-8.0-Config-File>
>      >
>      > Would be nice to move on it sooner rather than later.
>      >
>      > --Steve
>      >
>      >
>      > _______________________________________________
>      > mapserver-dev mailing list
>      > mapserver-dev at lists.osgeo.org <mailto:mapserver-dev at lists.osgeo.org>
>      > https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>      >
> 
> 
>     -- 
>     Daniel Morissette
>     Mapgears Inc
>     T: +1 418-696-5056 #201
>     _______________________________________________
>     mapserver-dev mailing list
>     mapserver-dev at lists.osgeo.org <mailto:mapserver-dev at lists.osgeo.org>
>     https://lists.osgeo.org/mailman/listinfo/mapserver-dev
> 
> 
> 
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>