tomcat

Travis CI Build Status Semantic Release

Formula to set up and configure tomcat webserver

1. General notes

See the full SaltStack Formulas installation and usage instructions.

If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.

If you want to use this formula, please pay attention to the FORMULA file and/or git tag, which contains the currently released version. This formula is versioned according to Semantic Versioning.

See Formula Versioning Section for more details.

If you need (non-default) configuration, please pay attention to the pillar.example file and/or Special notes section.

2. Contributing to this repo

Commit message formatting is significant!!

Please see How to contribute for more details.

3. Special notes

None

4. Available states

4.1. tomcat

Installs Tomcat and starts the service. The main configuration files are not changed, and the distro’s defaults are preserved as they come in the package.

4.2. tomcat.config

Configures the configuration file. Sane defaults are provided for the major Linux distros (Debian, RedHat, Arch) and their derivatives.

4.3. tomcat.native

Installs Apache Portable Runtime for Tomcat. Depends on tomcat.config to manage the configuration.

4.4. tomcat.manager

Installs the host-manager and manager web applications for Apache Tomcat.

4.5. tomcat.vhosts

Configures Tomcat name-based virtual hosts using data from Pillar.

4.6. tomcat.expires

Enables Tomcats' ExpiresFilter using data from Pillar.

4.7. tomcat.cluster

Configures Tomcat simple TCP cluster using data from Pillar.

4.8. tomcat.context

Configures context element in the $CATALINA_BASE/conf/context.xml file: the information in this file will be loaded by all web applications. (Check the context examples in the pillar.example file for more information.

5. Testing

Linux testing is done with kitchen-salt.

5.1. Requirements

  • Ruby

  • Docker

$ gem install bundler
$ bundle install
$ bin/kitchen test [platform]

Where [platform] is the platform name defined in kitchen.yml, e.g. debian-9-2019-2-py3.

5.2. bin/kitchen converge

Creates the docker instance and runs the TEMPLATE main state, ready for testing.

5.3. bin/kitchen verify

Runs the inspec tests on the actual instance.

5.4. bin/kitchen destroy

Removes the docker instance.

5.5. bin/kitchen test

Runs all of the stages above in one go: i.e. destroy + converge
verify + destroy.

5.6. bin/kitchen login

Gives you SSH access to the instance for manual testing.