Hey, glad you’re enjoying TypeType, and thx for reporting this. Dirk is right about the port mapping: the first port is on your host, the second is inside the container.

With the current Compose setup, set HOST_PORT_SERVER=18080 in .env. That maps host port 18080 to port 8080 inside the container. Keep the container port as 8080, since the health check and the other services use typetype-server:8080 internally. Changing only the host port shouldn’t make the server unhealthy.

You can check the health endpoint from inside the container with:

docker compose exec -T typetype-server wget -qO- http://127.0.0.1:8080/health

If it’s still unhealthy, could you share the typetype-server port mapping and the relevant startup lines from docker compose logs --tail=50 typetype-server? Please leave out any secrets.

You’re right that the README’s setup section is brief. The step-by-step guides are here:

• Quick Start
• Manual Docker Compose setup
• Port configuration
• Troubleshooting

You could leave the port on the container unchanged and just bind a random host port to the container, so the containered application doesn't know anything about the changed port.