Automate Java Code Analysis with SonarCloud & GitHub Actions 

Glad it was helpful!

Very informative

Glad it was helpful!

You can store environment variable details in GitHub secrets and then you can access those variables in your workflow. While building docker image you need to pass build arguments and set them in docker file. Ex: docker build -t your-image-name --build-arg AP|_KEY=${ secrets.AP|_KEY }. While in docker file you can set these as: # Dockerfile FROM node:14 # Set environment variable ARG APIKEY ENV AP|_KEY=$API_KEY # Other Dockerfile instructions

Glad it was helpful!

You're right, SonarCloud (and static code analysis tools in general) can't entirely prevent bugs due to logic errors. They primarily focus on identifying code smells, potential vulnerabilities, and enforcing coding standards.

Ensure that your EC2 instance is running and has passed its status checks. If the instance is stopped or terminated, you won't be able to access it. Verify that the security group associated with your EC2 instance allows inbound traffic on port 3000 from your IP address or from all IP addresses (0.0.0.0/0) if it's a public-facing service. Sometimes changes to security group rules may take a few moments to propagate.

@@IntegrationNinjasthanks it's working now on port 443