<commit_before># camunda BPM platform docker images

This camunda BPM community project provides docker images of the latest camunda
BPM platform releases.  The images can be used to demonstrate and test the
camunda BPM platform or can be extended with own process applications. It is
planed to provide images on the official [docker registry][] for every upcoming
release, which includes alpha releases.


## Get started

To start the latest release:

```
docker pull camunda/camunda-bpm-platform:latest
docker run -d --name camunda -p 8080:8080 camunda/camunda-bpm-platform:latest
# open browser with url: http://localhost:8080/camunda/
```

## Supported Tags/Releases

- `tomcat-7.2.0`, `tomcat-latest`, `latest` ([Dockerfile][tomcat-7.2.0])
- `jboss-7.2.0`, `jboss-latest` ([Dockerfile][jboss-7.2.0])
- `wildfly-7.2.0`, `wildfly-latest` ([Dockerfile][wildfly-7.2.0])

## Java Version

All images have Oracle JDK installed. The tomcat and wildfly image use
JDK 8 and the jboss image uses JDK 7.


## Environment variables

The used database can be configured by providing the following environment
variables:

- `DB_DRIVER` the database driver class name (**Note**: use for jboss and wildfly only
  the database identifier `h2`, `mysql` or `postgresql`)
- `DB_URL` the database jdbc url
- `DB_USERNAME` the database username
- `DB_PASSWORD` the database password

For example to use a postgresql docker image as database you can start the
platform as follows:

```
# start postgresql image with database and user configured
docker run -d --name postgresql ...

docker run -d --name camunda -p 8080:8080 --link postgresql:db \
           -e DB_DRIVER=org.postgresql.Driver \
           -e DB_URL=jdbc:postgresql://db:5432/process-engine \
           -e DB_USERNAME=camunda \
           -e DB_PASSWORD=<PASSWORD> \
           camunda/camunda-bpm-platform:latest
```

Another option is to save the database config to an environment file, i.e.
`db-env.txt`:

```
DB_DRIVER=org.postgresql.Driver
DB_URL=jdbc:postgresql://db:5432/process-engine
DB_USERNAME=camunda
DB_PASSWORD=<PASSWORD>
```

and use this file to start the container:

```
docker run -d --name camunda -p 8080:8080 --link postgresql:db \
           --env-file db-env.txt camunda/camunda-bpm-platform:latest
```

The docker image already contains drivers for `h2`, `mysql` and `postgresql`.
If you want to use other databases you have to add the driver to the container.


## Volumes

The camunda BPM platform is installed inside the `/camunda` directory. Which
means the tomcat configuration files are inside the `/camunda/conf/` directory
and the deployments on tomcat are in `/camunda/webapps/`. The directory
structure depends on the application server.

## Use Cases


### Change Configuration Files

You can use docker volumes to link your own configuration files inside the
container.  For example if you want to change the `bpm-platform.xml` on tomcat:

```
docker run -d --name camunda -p 8080:8080 \
           -v $PWD/bpm-platform.xml:/camunda/conf/bpm-platform.xml \
           camunda/camunda-bpm-platform:latest

```


### Add Own Process Application

If you want to add an own process application to the docker container also use
volumes. For example if you want to deploy the [twitter demo][] on tomcat:

```
docker run -d --name camunda -p 8080:8080 \
           -v /PATH/TO/DEMO/twitter.war:/camunda/webapps/twitter.war \
           camunda/camunda-bpm-platform:latest
```

This also allows you to modify the app outside of the container and it will
be redeployed inside the platform.


### Clean Distro Without Webapps and Examples

To remove all webapps and examples from the distro and only deploy your
own applications or your own configured cockpit also use volumes. You
only have to overlay the deployment folder of the application server with
a directory on your local machine. So in tomcat you would mount a directory
to `/camunda/webapps/'

```
docker run -d --name camunda -p 8080:8080 \
           -v $PWD/webapps/:/camunda/webapps/ \
           camunda/camunda-bpm-platform:latest
```


### Extend Docker Image

As we release these docker images on the offical [docker registry][] it is
easy to create your own image. This way you can deploy your applications
with docker or provided an own demo image. Just specify in the `FROM`
clause which camunda image you want to use as a base image:

```
FROM camunda/camunda-bpm-platform:tomcat-7.2.0

ADD my.war /camunda/webapps/my.war
```


## Maintainer

[<NAME>][]


## License

Apache License, Version 2.0


[tomcat-7.2.0]: Dockerfile
[jboss-7.2.0]: https://github.com/camunda/docker-camunda-bpm-platform/blob/jboss-7.2.0/Dockerfile
[wildfly-7.2.0]: https://github.com/camunda/docker-camunda-bpm-platform/blob/wildfly-7.2.0/Dockerfile
[<NAME>enski]: https://github.com/menski
[twitter demo]: https://github.com/camunda/camunda-consulting/tree/master/showcases/twitter
[docker registry]: https://registry.hub.docker.com/u/camunda/camunda-bpm-platform/<commit_msg>chore(README): use full url for master Dockerfile<commit_after># camunda BPM platform docker images

This camunda BPM community project provides docker images of the latest camunda
BPM platform releases.  The images can be used to demonstrate and test the
camunda BPM platform or can be extended with own process applications. It is
planed to provide images on the official [docker registry][] for every upcoming
release, which includes alpha releases.


## Get started

To start the latest release:

```
docker pull camunda/camunda-bpm-platform:latest
docker run -d --name camunda -p 8080:8080 camunda/camunda-bpm-platform:latest
# open browser with url: http://localhost:8080/camunda/
```

## Supported Tags/Releases

- `tomcat-7.2.0`, `tomcat-latest`, `latest` ([Dockerfile][tomcat-7.2.0])
- `jboss-7.2.0`, `jboss-latest` ([Dockerfile][jboss-7.2.0])
- `wildfly-7.2.0`, `wildfly-latest` ([Dockerfile][wildfly-7.2.0])

## Java Version

All images have Oracle JDK installed. The tomcat and wildfly image use
JDK 8 and the jboss image uses JDK 7.


## Environment variables

The used database can be configured by providing the following environment
variables:

- `DB_DRIVER` the database driver class name (**Note**: use for jboss and wildfly only
  the database identifier `h2`, `mysql` or `postgresql`)
- `DB_URL` the database jdbc url
- `DB_USERNAME` the database username
- `DB_PASSWORD` the database password

For example to use a postgresql docker image as database you can start the
platform as follows:

```
# start postgresql image with database and user configured
docker run -d --name postgresql ...

docker run -d --name camunda -p 8080:8080 --link postgresql:db \
           -e DB_DRIVER=org.postgresql.Driver \
           -e DB_URL=jdbc:postgresql://db:5432/process-engine \
           -e DB_USERNAME=camunda \
           -e DB_PASSWORD=<PASSWORD> \
           camunda/camunda-bpm-platform:latest
```

Another option is to save the database config to an environment file, i.e.
`db-env.txt`:

```
DB_DRIVER=org.postgresql.Driver
DB_URL=jdbc:postgresql://db:5432/process-engine
DB_USERNAME=camunda
DB_PASSWORD=<PASSWORD>
```

and use this file to start the container:

```
docker run -d --name camunda -p 8080:8080 --link postgresql:db \
           --env-file db-env.txt camunda/camunda-bpm-platform:latest
```

The docker image already contains drivers for `h2`, `mysql` and `postgresql`.
If you want to use other databases you have to add the driver to the container.


## Volumes

The camunda BPM platform is installed inside the `/camunda` directory. Which
means the tomcat configuration files are inside the `/camunda/conf/` directory
and the deployments on tomcat are in `/camunda/webapps/`. The directory
structure depends on the application server.

## Use Cases


### Change Configuration Files

You can use docker volumes to link your own configuration files inside the
container.  For example if you want to change the `bpm-platform.xml` on tomcat:

```
docker run -d --name camunda -p 8080:8080 \
           -v $PWD/bpm-platform.xml:/camunda/conf/bpm-platform.xml \
           camunda/camunda-bpm-platform:latest

```


### Add Own Process Application

If you want to add an own process application to the docker container also use
volumes. For example if you want to deploy the [twitter demo][] on tomcat:

```
docker run -d --name camunda -p 8080:8080 \
           -v /PATH/TO/DEMO/twitter.war:/camunda/webapps/twitter.war \
           camunda/camunda-bpm-platform:latest
```

This also allows you to modify the app outside of the container and it will
be redeployed inside the platform.


### Clean Distro Without Webapps and Examples

To remove all webapps and examples from the distro and only deploy your
own applications or your own configured cockpit also use volumes. You
only have to overlay the deployment folder of the application server with
a directory on your local machine. So in tomcat you would mount a directory
to `/camunda/webapps/'

```
docker run -d --name camunda -p 8080:8080 \
           -v $PWD/webapps/:/camunda/webapps/ \
           camunda/camunda-bpm-platform:latest
```


### Extend Docker Image

As we release these docker images on the offical [docker registry][] it is
easy to create your own image. This way you can deploy your applications
with docker or provided an own demo image. Just specify in the `FROM`
clause which camunda image you want to use as a base image:

```
FROM camunda/camunda-bpm-platform:tomcat-7.2.0

ADD my.war /camunda/webapps/my.war
```


## Maintainer

[<NAME>][]


## License

Apache License, Version 2.0


[tomcat-7.2.0]: https://github.com/camunda/docker-camunda-bpm-platform/blob/master/Dockerfile
[jboss-7.2.0]: https://github.com/camunda/docker-camunda-bpm-platform/blob/jboss-7.2.0/Dockerfile
[wildfly-7.2.0]: https://github.com/camunda/docker-camunda-bpm-platform/blob/wildfly-7.2.0/Dockerfile
[<NAME>]: https://github.com/menski
[twitter demo]: https://github.com/camunda/camunda-consulting/tree/master/showcases/twitter
[docker registry]: https://registry.hub.docker.com/u/camunda/camunda-bpm-platform/
{'fraction_non_alphanumeric': 0.10247524752475247, 'fraction_numerical': 0.0201980198019802, 'mean_word_length': 3.7378048780487805, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 11, 'lorem ipsum': 0, 'www.': 0, 'xml': 6}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2417374', 'n_tokens_mistral': 3332, 'n_tokens_neox': 3086, 'n_words': 1139}