brucepc / mapguide Goto Github PK

Hi Bruce,

I saw your keen interest on a lightweight MapGuide docker image. Unfortunately my developer priorities are such that I won't be able to look at building a production quality docker image (the one I put on docker hub is really a toy). If you're happy to take on this task, then I have some ideas you could possibly explore :)

One thing I'd really like to see is a separation of the MapGuide docker image into its respective server and web tiers.

• Server-only image
  • Must be Ubuntu14 or CentOS6 based as that is what MapGuide is built against
  • A server-only docker image that only contains the contents of /usr/local/mapguideopensource/server and /usr/local/mapguideopensource/share
  • Configurable elements
    • Listening ports
    • Volume paths for
      • External spatial data files (that MapGuide can reference through external aliases and that can be shared among multiple MG server docker containers)
• WebTier-only image
  • Must be Ubuntu14 or CentOS6 based as that is what MapGuide is built against
  • A web-only docker image that only contains the contents of /usr/local/mapguideopensource/webserverextensions and /usr/local/mapguideopensource/share
  • Configurable elements
    • Listening HTTP port
    • 1 or more sets of server IP/ports
    • Volume paths for
      • Referencing/storing your MapGuide application's files

A killer setup with this approach would be if I can make a docker-compose.yml (or any other container orchestrator of your choice) consisting of

• 1 WebTier container with my application files mounted
• 1-n load-balanced Server containers
• A PostGIS or OracleXE container that all server containers connect to

One docker-compose up would bring this load-balanced PostGIS/Oracle/MapGuide stack to life.

MG ports are only for the Web Tier (that resides in the same container) to communicate with mgserver.

Tomcat port is only so that Apache (also in the same container) can talk to it.

Only the httpd one (8008) needs to be visible to the outside world.

The QuickPlot widget currently cannot generate PDF plots because of this

I see you're trying to symlink Access.log, Admin.log and Authentication.log to /dev/stdout, but I don't think that is working properly because the console output after docker run is very quiet and if I exec into the container, I see this in the Logs directory

Something you might want to document about this container (in the readme or elsewhere)

If using docker port mapping to a different port (eg. docker run -p 80:8008 ...), QuickPlot will break as while the initial POST to PlotAsPDF.php will work, that script needs to internally make a request to GeneratePicture.php, by constructing a URL relative to the $_SERVER["SCRIPT_URI"] of PlotAsPDF.php.

As PlotAsPDF.php was accessed through its external port (80), the URL constructed to GeneratePicture.php is invalid because the httpd server inside the container is still listening on 8008.

I don't know what tricks we can use in PHP to make QuickPlot work in this type of setup. The only workaround is to map to the same port number externally

How install and configuration unixODBC in mapguide