We provide two different containerized Wildbooks using Docker. Unless you are setting up a production instance of Wildbook, use the Development Docker option.
All support materials are found in the devops/development/
subdirectory. This launches docker containers sufficient for you to deploy a wildbook.war
file which you have developed
via your own Java environment.
.env
file - see below.sudo sysctl -w vm.max_map_count=262144
(A requirement for OpenSearch, it only needs to be run once on your system.)devops/development/
folder, create a .env
file with a copy the contents of _env.template
. By default, no changes should be needed, but you can edit this new file if needed.WILDBOOK_BASE_DIR
from .env
file above) and the required subdirectories. The default is ~/wildbook-dev/
). For example:
mkdir -p ~/wildbook-dev/webapps/wildbook
mkdir ~/wildbook-dev/logs
.war
file (see section below) in the above wildbook/
directory, using jar
:
cd ~/wildbook-dev/webapps/wildbook
jar -xvf /path/to/wildbook-xxx.war
devops/development/
directory in the wildbook repodocker-compose up [-d]
, which launches all of the aforementioned docker imagestomcat
/tomcat123
should work.To run Wildbook in the development docker environment, even to try out the software, you need a “war file” which is made by compiling the Wildbook java project. This requires some software to be set up on your development machine:
openjdk
) and build-essential
linux package, as well as maven
[probably a link to generic setup doc elsewhere?]Once the above requirements are met, the war file can be created by running mvn clean install
. This creates the war file to be used in target/wildbook-X.Y.Z.war
(with current version number).
If you make code changes and compile new war files, they can be deployed into the wildbook
dir (as in step 3 above) and then tomcat restarted with
docker-compose restart wildbook
.
This image and all support materials are found in the deploy/
subdirectory. Run Wildbook and required docker images for production installations only.
THIS IS CURRENTLY UNDER DEVELOPMENT - DRAFT ONLY
This launches an instance of Wildbook for the sake of testing or using in production. It can be used to deploy on a VM/host on the internet or locally.
The following docker containers should launch if started with docker-compose [-d] up
. Some of these are “optional” as noted below.
To skip optional containers, you should launch explicitly including the ones you want, such as: docker-compose up db wildbook
.
Currently, nginx is not configured to support ssl/https certs. There are some notes in the nginx conf about potential solutions.
_env.template
to .env
and edit this new file with your own valuesdocker-compose up ....
If you want to run Wildbook on non-dockerized tomcat, the system will likely build, but functionality will be restricted (i.e., search will not work) and additional functionality will likely break as we continue modernizing the stack. That being said, good luck!