-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
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/serverand/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/webserverextensionsand/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.
brucepc and scsabi
Metadata
Metadata
Assignees
Labels
No labels