Java + Tomcat + PostgreSQL

Apache Tomcat as a servlet container and PostgreSQL as the database.

The Tomcat Stack variant for projects that already work with PostgreSQL or that need its advanced data types, such as native JSON or full-text search.

Included services

In addition to your application, the Stack brings up PostgreSQL, an nginx that receives traffic on port 80, an automatic backups service and the web file manager.

Project structure

text

.
├── app
│   ├── META-INF
│   │   └── MANIFEST.MF
│   ├── WEB-INF
│   │   ├── ...
│   │   └── web.xml
│   ├── images
│   │   └── tomcat.gif
│   ├── MANIFEST.MF
│   ├── hello.jsp
│   ├── index.html
│   └── status.json
├── backup
│   └── backup-runner.sh
├── nginx
│   └── default.conf
├── .env.example
├── app.Dockerfile
└── compose.yaml

Getting started

Install the Stack and bring it up:

bash

docker-deploy-stack --stack java/tomcat-postgres
cd /root/stack/java/tomcat-postgres
docker compose up -d

Then replace the example application with yours, via Git, by SFTP or from the web file manager, following como-despliego-una-aplicacion-en-un-stack.md. Your code goes in the app/ folder.

Each time you update the code, apply the changes:

bash

docker compose up -d --build

Configuration

Editable values are in the Stack’s .env file:

Variable	Default	Purpose
`APP_PORT`	`80`	Public port of the Stack.
`APP_ENV`	`development`	Application environment.
`DB_NAME`	`example`	Database name.
`BACKUP_ENABLED`	`1`	Automatic backups: `1` enabled, `0` disabled.
`BACKUP_INTERVAL_SECONDS`	`86400`	How many seconds between backups.
`BACKUP_RETENTION_DAYS`	`7`	How many days backups are kept.
`POSTGRES_VERSION`	`16-alpine`	Version of the corresponding image.

After changing it, apply the changes with docker compose up -d.

Useful commands

bash

docker compose ps          # see the containers that are running
docker compose logs -f     # view live logs
docker compose restart     # restart the services
docker compose down        # stop and remove the containers