# Tommy

Tommy is a tiny, single-file, fully configurable Apache Tomcat web server for running or embedding static and dynamic (JSP and Servlet) web applications. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5118/tommy

## Description

Tommy is a tiny, single-file, fully configurable Apache Tomcat web server for running or embedding static and dynamic (JSP and Servlet) web applications. It ships as a single executable jar with no dependencies or installation required and uses standard Tomcat configuration files, so developers and homelab builders can drop in apps as directories or WAR/ZIP archives.

## Platform availability

Available on 0 of 10 platforms.

## Health score

24/100 (Low), based on 4 of 5 factors.
- Maintained: 0 (last commit 1861 days ago)
- Popular: 20 (9 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Security check: 75 (no serious findings)

## Links

- GitHub: https://github.com/xnbox/tommy
- Docker Hub: https://hub.docker.com/r/nasqueron/tommy
- Official website: https://builds.nasqueron.org

## Common questions

### Can TOMMY be run in Docker without Home Assistant?

Yes. TOMMY can be run as a standalone Docker container for self-hosted setups and users who want to run TOMMY independently of Home Assistant.

### What TCP ports does Tommy use by default?

It uses TCP port 8080 for HTTP and TCP port 8443 for HTTPS by default. You can change them with --port and --port-ssl.

### Can Tommy serve an app from a subpath instead of the root URL?

Yes, use --context-path to set the context path. The default context path is /.

### Where does Tommy read its Apache Tomcat configuration files?

Tommy uses the Apache Tomcat configuration files from the /META-INF/tomcat/conf directory of the tommy.jar archive.

---
Source: Our Local Host (https://ourlocalhost.com/app/5118/tommy), the self-hosted and open-source app directory.
