Easytravel-nginx

NGINX reverse-proxy component of the Dynatrace easyTravel demo application.

  • Network Services
NGINX reverse-proxy component of the Dynatrace easyTravel demo application. It routes incoming visitor requests to the easyTravel travel-booking frontend so the full multi-tier application (MongoDB database, Java backend, and frontend with load generator) runs as a realistic demonstration. Run it when standing up the easyTravel demo to observe how a modern website handles traffic under observability tooling.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

48/100 Fair

Maintained
67last commit 88 days ago
Popular
3767 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
67
Open issues
12
Last commit
2026-08-25
Activity
stale

Checked 15 days ago - source: GitHub (Dynatrace/easyTravel-Docker)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Images and building from source All easyTravel components, including this NGINX image, are published on Docker Hub under the dynatrace namespace and can be pulled directly. To build the deployment artefacts from source, run build-in-docker.sh from the repository, which creates a deploy directory in your working directory. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should easytravel-nginx terminate TLS for backend requests to the travel-site sections?

Generally, terminate SSL at the reverse proxy and use plain connections to backend servers if those connections do not leave the LAN.

What should I share when an easytravel-nginx route is not reaching the intended section?

Share the Nginx configuration and the enabled-sites configs, after replacing any sensitive information.

How can I keep multiple easytravel site configs easier to maintain?

Use the include directive for common options so each site config file is smaller and easier to maintain and update.

What packaging detail is preferred before adding easytravel-nginx as a one-click self-hosted template?

The thread says it is looking for self-hosted apps that are already containerized for Docker.

Answers sourced from www.reddit.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads