Description
Actually the docker file of MapStore downloads release binary by default in any case.
This is quite confusing, because if we build on a different branch, we get anyway the latest version of the war. This doesn't happen on our build servers because we override the variable MAPSTORE_WEBAPP_SRC to customize the file path.
- It could be better to get the docker file builds file from the current build folder (
MAPSTORE_WEBAPP_SRC) , creating a docker image consistent with the current branch, without any needing to customize. Something like ./web/target/mapstore.war (in product ./product/target/mapastore.war)
- maybe avoid multiple copies of
mapstore.war and allow override of the mapstore.war as a volume also on run time.
- Properly document docker image usage (and cases with printing profile).
- Moreover could be good if we can reuse the same docker file to build a docker image for projects. We have to study a solution, maybe using docker layers, reusing the docker file of the sub-module.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
Description
Actually the docker file of MapStore downloads release binary by default in any case.
This is quite confusing, because if we build on a different branch, we get anyway the latest version of the war. This doesn't happen on our build servers because we override the variable
MAPSTORE_WEBAPP_SRCto customize the file path.MAPSTORE_WEBAPP_SRC) , creating a docker image consistent with the current branch, without any needing to customize. Something like./web/target/mapstore.war(in product./product/target/mapastore.war)mapstore.warand allow override of themapstore.waras a volume also on run time.What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information