A dockerized container for the BalticWeb project. The container deploys the latest successful build of BalticWeb on a Wildfly 8.2.0 web server. It also has the required CouchDB and MySQL as described in the BalticWeb guide.
- Docker 1.10.0+
- Docker Compose 1.6.0+
- A file called balticweb.properties
- Two configuration files for Keycloak as described in BalticWeb
Clone the repository to a chosen directory using and go the directory containing the Docker files
$ git clone https://github.com/maritime-web/BalticWeb.git $ cd BalticWeb/docker
In your home directory you need to make two new directories - 'balticweb/properties' and 'balticweb/couchdb'. The latter needs to have the subdirectory 'couchdb/etc/local.d'.
In the 'balticweb/properties' directory you should put the 'balticweb.properties' file, and in 'balticweb/couchdb/etc/local.d' you should put the configuration files you wish to use for the CouchDB.
It is recommended to also put the configuration files for Keycloak in the 'balticweb/properties' directory. In 'balticweb.properties' you should then override the default configuration with the following:
If you want to build the BalticWeb container yourself do the following, but you only need to do this if you have a specific reason to do it
$ docker build -t dmadk/balticweb .
Currently there are two ways of starting the BalticWeb container and the two databases.
The first is using Docker Compose. On the first startup do
$ docker-compose up
On subsequent startups you can start with either
$ docker-compose up
$ docker-compose start
To stop use either
$ docker-compose stop
$ docker-compose down
The second way of starting is using the script deploy.sh which also makes a WatchTower container which makes sure that the latest version of BalticWeb is always running.
On the first startup using this method do
$ chmod +x deploy.sh $ chmod +x undeploy.sh $ ./deploy.sh full
On subsequent startups do
When you want to stop the containers do
If you want to stop the containers and then remove them do
$ ./undeploy.sh full