npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

generator-jhipster-azure-container-apps

v1.0.9

Published

CLI for JHipster Azure Container Apps

Readme


NPM version

Introduction

JHipster Azure Container Apps enables developers to rapidly create and deploy full-stack Java applications on Azure Container Apps with minimal steps. This integration simplifies the deployment process, allowing seamless scalability and management for both frontend, backend and database services on Azure.

Prerequisites

As this is a JHipster blueprint, we expect you have JHipster basic knowledge:

The following prerequisites arer equired to run this application locally. Please ensure that you have them all installed locally.

The following prerequisites arer equired to deploy this application to Azure.

🚀 Get Started

npm install -g generator-jhipster-azure-container-apps

🚁 How to run locally

To use JHipster Azure Container Apps, run the below command

jhipster-azure-container-apps

You can look for updated azure-container-apps blueprint specific options by running

jhipster-azure-container-apps app --help

To run locally:

  • For back-end, you can build manually under src/api with:
mvn clean package -DskipTests
java -jar target/{artifactname}-0.0.1-SNAPSHOT.jar
  • The back-end can be accessed at:
http://localhost:3100/
  • For front-end, you can build manually under src/web with:
npm install
npm run dev
  • The front-end can be accessed at:
http://localhost:3000/

🎉 How to deploy on Azure with free grants

JHipster Azure Container Apps provides multiple ways to deploy on Azure, you can deploy with the built-in Terraform, Bicep, Azure Developer CLI(AZD) or directly from source code.

Terraform

  1. Make sure you marked Terraform when generating the project.
  2. Make sure you have Terraform installed and configured.
  3. Change into the Terraform folder: cd terraform
  4. Run the following command to initialize Terraform: terraform init
  5. Once finished, privision the necessary resource on Azure with: terraform apply -auto-approve
  6. Now you can deploy the project with:
    • Linux/MacOS: .\deploy.sh. You can run the deployment script by adding options subId, region and resourceGroupName.
    • Windows: .\deploy.ps1. You will be prompted to provide subId, region, and resourceGroupName.

Bicep

  1. Make sure you marked Bicep when generating the project.
  2. Make sure you have Azure CLI installed and configured.
  3. Change into the bicep folder: cd bicep
  4. Setup bicep with: az deployment sub create -f ./main.bicep --location=eastus2 --name jhipster-aca --only-show-errors Here you can replace the location and the name parameters with your own choices.
  5. Now you can deploy the project with:
    • Linux/MacOS: .\deploy.sh. You can run the deployment script by adding options subId, region and resourceGroupName.
    • Windows: .\deploy.ps1. You will be prompted to provide subId, region, and resourceGroupName.

Azure Developer CLI(AZD)

  1. Make sure you have Azure Developer CLI installed and configured.
  2. Log in to AZD, only required once per-install. azd auth login
  3. Navigate to the generated project directory and run azd up Make sure your docker is running when executing this.

After the command is executed, you can see the following log signs that the deployment was successful.

SUCCESS: Your up workflow to provision and deploy to Azure completed in <deployment-time>.

Deploy from artifact, source code, IDE and more

In addition to the options mentioned, Azure Container Apps offers a variety of deployment methods, all simplified by its built-in Java support. Explore how to easily deploy your project by visiting: Launch your first Java application in Azure Container Apps.

The output Deploying service api and Deploying service web are the endpoints to access the todo application.

❤️ Next Steps

Azure Container Apps has built-in Java support to enhance your Java applications with automatic memory fitting, diagnostics and managed spring componnets, learn more. You can easily turn on the Java support feature by clicking on the manage of the Development stack and choose Java on your overview page. Java Stack.