# Using Java with NubesGen
This documentation is for running Java applications with NubesGen. There are three other options that might interest you:
- You can use Spring Boot with NubesGen, which is similar to Java, but uses the specific Spring Boot application properties.
- You can use Quarkus with NubesGen, which uses the specific Quarkus application properties.
- As Java applications can be packaged with Docker, you can also run them as Docker applications with NubesGen.
NubesGen supports creating Azure App Service instances and Azure Functions instances, depending on the type of Java application that you wish to deploy.
# Tutorial: running a Java application with NubesGen
Prerequisites:
Tip: You can go to https://aka.ms/nubesgen-azure-shell (opens new window) to have those prerequisites installed, and run the script from a Web browser.
- Bash (opens new window), which is installed by default on most Linux distributions and on Mac OS X. If you're using Windows, one solution is to use WSL (opens new window).
- Azure CLI (opens new window). To login, use
az login
. - (optional) GitHub CLI (opens new window). To login, use
gh auth login
.
Steps:
- Create a sample Java Web application using https://start.spring.io/ (opens new window).
curl https://start.spring.io/starter.tgz?type=maven-project&language=java&bootVersion=3.1.3&baseDir=java-sample-app&groupId=com.example&artifactId=java-sample-app&name=java-sample-app&description=Demo%20project%20for%20Spring%20Boot&packageName=com.example.java-sample-app&packaging=jar&javaVersion=17&dependencies=web | tar -xzvf -
- Create a project on GitHub called
java-sample-app
, and push the generated project to that repository. Change<your-github-account>
to the name of your GitHub account:cd java-sample-app git init git add . git commit -m "first commit" git remote add origin https://github.com/<your-github-account>/java-sample-app.git git branch -M main git push -u origin main
- In the cloned project (
cd java-sample-app
), set up GitOps with NubesGen by running the NubesGen CLI (more information here):./nubesgen-cli-linux gitops
- Use the command-line with NubesGen (more information here) to generate a NubesGen configuration:
curl "https://nubesgen.com/demo.tgz?runtime=java&application=app_service.standard&gitops=true" | tar -xzvf -
- Create a new branch called
env-dev
, and push your code:git checkout -b env-dev git add . git commit -m 'Configure GitOps with NubesGen' git push --set-upstream origin env-dev
- Go to your GitHub project, and check that the GitHub Action is running.
- You can go to the Azure Portal (opens new window) to check the created resources.
- The application should be deployed on your App Service instance. Its URL should be in the form
https://app-demo-XXXX-XXXX-XXXX-XXXX-dev-001.azurewebsites.net/
, and you can also find it in the GitHub Action workflow (Job: "display-information", step "Display Azure infrastructure information"), or in the Azure portal. As it is an empty application, you should get 404 page calledWhitelabel Error Page
. - Once you have finished, you should clean up your resources:
- Delete the resource group that was created by NubesGen to host your resources, which is named
rg-demo-XXXX-XXXX-XXXX-XXXX-001
. - Delete the storage account used to store your Terraform state, in the
rg-terraform-001
resource group.
- Delete the resource group that was created by NubesGen to host your resources, which is named
# Which Azure resources are created
If you deploy your Java application to an Azure App Service instance, NubesGen will generate:
- An Azure App Service plan (opens new window) to define the type of App Service instance you will use.
- An Azure App Service instance (opens new window), configured to run Java code natively.
If you deploy your Java application to an Azure Function, NubesGen will generate:
- An Azure App Service plan (opens new window) to define the type of Azure Functions instance you will use.
- An Azure Functions instance (opens new window), configured to run Java code natively.
- An Azure Storage Account (opens new window), to store your Java application.
# Maven vs Gradle
NubesGen supports both Maven and Gradle, so you can use the build system you prefer.
# Configuration options
In the generated terraform/modules/app-service/main.tf
file, NubesGen will configure some environment variables
for your application.
DATABASE_URL
: the URL to your databaseDATABASE_USERNAME
: the database user nameDATABASE_PASSWORD
: the database passwordREDIS_HOST
: the Redis host nameREDIS_PASSWORD
: the Redis passwordREDIS_PORT
: the Redis port (by default6380
)AZURE_STORAGE_ACCOUNT_NAME
: the storage account nameAZURE_STORAGE_ACCOUNT_KEY
: the storage account keyAZURE_STORAGE_BLOB_ENDPOINT
: the blob storage endpointMONGODB_DATABASE
: the MongoDB database nameMONGODB_URI
: the MongoDB database URL