← Directory

JHipster Elasticsearch Sample

JHipster Elasticsearch Sample is a reference Spring Boot web application generated with JHipster.

  • Tools & Utilities
JHipster Elasticsearch Sample is a reference Spring Boot web application generated with JHipster. It demonstrates how to integrate Elasticsearch for full-text search and document indexing in a Java web app using the JHipster Elasticsearch connector. It is intended as a working example for developers evaluating or learning JHipster, not a production service.

Platform availability

Available on 0 of 6 install platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

52/100 Fair

Maintained
79last commit 22 days ago
Popular
3239 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

How is this calculated?

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). Factors without data are left out and the rest are rescaled.

GitHub stars
39
Open issues
5
Last commit
2026-09-18
License
Apache-2.0
Activity
rising

Checked 11 days ago - source: GitHub (jhipster/jhipster-sample-app-elasticsearch)

Resources & Compatibility

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

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

First-install notes

  • Fill in domain and email for Let's Encrypt Before running the certificate command, replace <your-domain.com> and <your-email> with your actual web address and email. This is how Let's Encrypt verifies you own the site, so if these are wrong your certificate will not be issued and visitors may get security errors. source
  • Open HTTP and HTTPS ports for Apache Make sure your firewall or cloud security group allows inbound traffic on port 80 (HTTP) and port 443 (HTTPS). Without these open, browsers cannot reach the site and Let's Encrypt cannot check the domain to issue a certificate. source
  • Keep the app JAR path available The Linux service (a background process managed by the OS) points to your application JAR (the packaged app file), so make sure the file exists at the expected path before starting the service. If the file is missing or renamed, the service will not start and the app will be down. source

Fetched 10 days ago - each note links to its source

Alternatives (2)

  • Portofino - Portofino is a free and open source web framework that helps developers create outstanding enterprise applications by addressing three spec…
  • jhipster - JHipster is a development tool used to quickly build modern web applications and services.

Checked 9 days ago - source: AlternativeTo

Common questions

How do I point the JHipster sample app at an external Elasticsearch instance in development?

In development, JHipster runs with an embedded Elasticsearch instance. You can use an external Elasticsearch instance by setting the SPRING_DATA_URIS environment variable or adding spring.elasticsearch.uris to application-dev.yml.

Will the Elasticsearch reindexer module work if Elasticsearch was not selected during app generation?

The JHipster Elasticsearch reindexer module only works if Elasticsearch is selected when generating the app. Search can be performed through the UI.

What host settings are needed before using Let's Encrypt and starting the Linux service?

Set the real domain and email before running the certificate command, because Let's Encrypt uses them to verify site ownership. Open inbound ports 80 and 443, and keep the application JAR at the path the Linux service expects. If the JAR is missing or renamed, the service will not start.

Answers sourced from github.com, stackoverflow.com, www.jhipster.tech

Community

Collected 5 days ago - public community threads