Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docker - provide unzipped war (#664)
* docker - provide unzipped war * take into account edevos review
- Loading branch information
ade5226
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fvanderbiest could you expand a bit about the meaning of this change please ?
What WARs are supposed to land in
/docker
before the docker build ?Is there a documentation about that ?
before this commit,
./build.sh
generated amapstore.war
that was usually copied to/docker
.Thanks for info.
ade5226
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Florent,
Did you see my comments on #664 ?
ade5226
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope I didn't see the link in the comment (thought that it was something from github), my bad !
ade5226
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TLDR: the
Dockerfile
works with the github action but not with the main build script.--
What is confusing is that the common way to build MapStore is with
./build.sh
. Thebuild.sh
script and theDockerfile
should be aligned.It seems that you are maintaining a github workflow which builds the project instead of the
build.sh
, and that you aligned theDockerfile
with it without back porting those changes to the./build.sh
, am I correct ?