This is exactly why PHP MapScript has been so popular for so long
("wrappers" of OGC services) and why so many examples of this exists in
the MapServer documentation. Honestly though, someday I also hope for a
more direct way to handle these dynamic changes, but until then,
#mapscriptrocks :)
Thanx for the suggestions Kaido, Seth, Steve. Updating the mapfile at
deployment indeed is a better option then the querystring approach, let me
verify what scripting options (sed?) i have on our docker image.
___
MapServer-users mailing list
Hi Paul,
We are using basically the same process as Seth and Steve mentioned.
We are building map files per environment and per node using Chef.
Basically we parameterized the .map file and fill in parameters for every
node when we deploy.
And because we have multiple map files for different
Hi Paul,
The runtime substitution and setting a querystring on the server is a good
approach - have you found any drawbacks to this? Most web servers can set/add
querystrings without any need for further software.
As Steve mentioned the alternative would be to generate Mapfiles for specific
