New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added extra options for geoserver #28
Conversation
NyakudyaA
commented
Feb 25, 2018
•
edited
edited
- Added a download script to install plugins in Geoserver. The script should be run before building the image. Some common plugins should be preinstalled in the image (ie control-flow, GDAL, WPS, Image pyramid)
- Added GDAL data directory and environment variables to ensure when a user installs the Gdal plugins Geoserver recognizes them.
- Moved the java environment settings to the docker file so that the image contains built-in optimizations.
- Modified build script so that when building the image locally you only specify the GeoServer version once in the download script and it changes all occurrences in other files. Example Dockerfile and download.sh.
- Added more instructions in the readme including how to use a persistent storage with sample data from GeoServer war file.
- Added a sample file for use with the control flow module.
- Install libjpeg-turbo- An extension which provides a significant performance enhancement for JPEG encoding in GeoServer WMS output
- Install extra fonts which are used by SLD with graphic markers
Dockerfile
Outdated
@@ -106,7 +153,7 @@ RUN rm -f /tmp/resources/overlays/README.txt && \ | |||
fi; | |||
|
|||
# Optionally remove Tomcat manager, docs, and examples | |||
ARG TOMCAT_EXTRAS=true | |||
#ARG TOMCAT_EXTRAS=true #moved to docker-compose.yml | |||
RUN if [ "$TOMCAT_EXTRAS" = false ]; then \ |
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.
because the previous line has been moved to docker-compose, this will always be false and therefore run - delete it? Or should it run?
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.
It should always be true. The arguments are substituted when building the image. So in the docker-compose, it would be
args:
- ORACLE_JDK=true
- TOMCAT_EXTRAS=false
LGTM - just address my one comment then merge (and test after merging) |
README.md
Outdated
The Tomcat properties such as maximum heap memory size are included in the Dockerfile. You need to change them | ||
them before building the image in accordance to the resources available on your server: | ||
|
||
The default settings in the image are: |
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.
I would delete this section - if the default settings change then this would have to be maintained
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.
I will delete that