Added readme file and npm install

Author: NeckerFree

Cloud README.md

@@ -76,19 +76,25 @@ This project automates the provisioning and deployment of a scalable cloud appli
 
 ### Key Features <a name="key-features"></a>
 
-- 🔧 Automated infrastructure provisioning with Terraform
-- 📦 Service configuration and app deployment using Ansible
-- 🌐 Scalable API on 2 Azure VMs behind a Load Balancer
-- 💾 Managed Azure MySQL integration
-- 🚀 Web frontend deployed using Azure Web App
+- 🔧 Automated infrastructure provisioning with Terraform  
+- 📦 Service configuration and app deployment using Ansible  
+- 🐘 MySQL database initialized via Ansible using `ansible/files/mysql/movie_db.sql`
+- 🌐 Scalable API on 2 Azure VMs behind a Load Balancer  
+- 💾 Managed Azure MySQL integration  
+- 🚀 Web frontend deployed using Azure Web App  
+- 🔐 Service Principal authentication using Client Secret  
+- ⚙️ Fully automated deployment workflow with CI/CD integration  
+- 🏗️ End-to-end Terraform deployment from scratch included in workflow  
+- 🧹 Automated environment teardown using `terraform-destroy.yml`  
+- 💸 Uses Azure Web App **F1 Free Tier** for cost-effective deployment  
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
 
 ---
 
 ## 🚀 Live Demo <a name="live-demo"></a>
 
-- [Frontend Web App](https://your-frontend-url.azurewebsites.net)
+- [Frontend Web App](https://softdefault-movies-app.azurewebsites.net/)
 - [API Endpoint (behind Load Balancer)](http://your-lb-ip-or-dns)
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
@@ -101,66 +107,112 @@ To get a local copy up and running, follow these instructions.
 
 ### Prerequisites
 
-- Azure CLI (`az`)
-- Terraform ≥ 1.5
-- Ansible ≥ 2.15
-- Python 3 with `msrestazure`, `azure-cli-core`, `requests`
-- SSH key pair
+Most dependencies are installed automatically in the GitHub Actions workflow. However, for local development or debugging, ensure you have the following:
 
-### Setup
+- 🖥️ Azure CLI (`az`)
+- 📦 Terraform ≥ 1.5
+- ⚙️ Ansible ≥ 2.15
+- 🔐 SSH key pair for accessing virtual machines
+- 📦 Node.js ≥ 14 and npm (required for both frontend and backend)
+- 📚 `zip` utility (used to package the frontend app)
+- ☁️ Azure Service Principal credentials (used by the workflow):
+  - `ARM_CLIENT_ID`
+  - `ARM_CLIENT_SECRET`
+  - `ARM_TENANT_ID`
+  - `ARM_SUBSCRIPTION_ID`
+- 💡 *(Optional)* GitHub CLI (`gh`) – useful for managing secrets or manually triggering workflows
 
-```bash
-git clone https://github.com/your-username/azure-cloud-webapp-deploy.git
-cd azure-cloud-webapp-deploy
-```
-
-## 📦 Provision Infrastructure (Terraform) <a name="terraform"></a>
 
-1. Initialize Terraform:
+### 🔧 Setup
 
 ```bash
-cd terraform/
-terraform init
+# Clone this repository
+git clone https://github.com/NeckerFree/azure-fullstack-automation.git
+cd azure-fullstack-automation
 ```
 
-2. Set your variables in `terraform.tfvars` or export them:
+## 📦 Provision Infrastructure (Terraform) <a name="terraform"></a>
 
-```bash
-terraform plan -out plan.tfout
-terraform apply "plan.tfout"
-```
+Infrastructure provisioning is fully automated and triggered via **GitHub Actions** on every push or pull request to the `main` branch.
 
-## ⚙️ Configure Services (Ansible) <a name="ansible"></a>
+- Terraform is initialized and executed within the workflow using predefined variables.
+- The deployment includes:
+  - A MySQL database on Azure
+  - A Load Balancer with 2 backend VMs
+  - Network and security resources
+- The entire infrastructure is provisioned from scratch via `terraform.yml`.
 
-1. Install Azure collection:
+## ⚙️ Configure Services (Ansible) <a name="ansible"></a>
 
-```bash
-ansible-galaxy collection install azure.azcollection
-```
+Once the infrastructure is up, **Ansible playbooks** are automatically triggered within the same CI/CD workflow to:
 
-2. Run Ansible Playbooks:
+- Configure the VMs with the required packages
+- Deploy the Node.js API to both backend nodes
+- Apply application settings
+- Validate MySQL schema creation and data population
 
-```bash
-cd ansible/
-ansible-playbook -i inventory.ini site.yml
-```
+This configuration is handled through the `deploy-api.yml` GitHub Actions workflow.
 
 ## 🚢 Deployment <a name="deployment"></a>
 
-- API is reachable via Load Balancer Public IP.
-- Web frontend is served via Azure Web App.
-- All backend components connect to Azure MySQL securely.
+- 🎯 **Trigger**: Every push or pull request to `main` kicks off a full deployment pipeline.
+- 🌐 **API** is publicly reachable via the Load Balancer’s IP address.
+- 💻 **Frontend** is deployed to Azure Web App using the **F1 Free Tier**.
+- 🔐 **Secure integration** between services via environment variables and Azure-managed credentials.
+- 🧨 A separate `terraform-destroy.yml` workflow is available to automatically destroy all infrastructure when needed.
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
 
+---
+## 🔧 Customizing Variables <a name="custom-variables"></a>
+
+You can modify the following variables to adapt the deployment to your needs. These are defined in the Terraform configuration files:
+
+### `infra/terraform.tfvars`
+
+```hcl
+allowed_ssh_ip        = "186.155.19.140/32"         # IP allowed to access VMs via SSH
+mysql_user            = "mysqladmin"                # MySQL admin user
+mysql_admin_password  = "Sec#reP@ssword123!"        # MySQL admin password
+
+variable "location" {
+  default = "westus2"                               # Azure region to deploy resources
+}
+
+variable "admin_username" {
+  default = "myadminuser"                                # Admin username for virtual machines
+}
+
+variable "lb_api_port" {
+  default = 8080                                    # API port exposed by Load Balancer
+}
+```
+---
+## ☁️ Remote Terraform State in Azure <a name="remote-state"></a>
+
+Terraform uses remote state storage to persist infrastructure state across executions and team members.
+
+This project stores the Terraform state file (`terraform.tfstate`) securely in an **Azure Storage Account** using a backend configuration like the following:
+
+```hcl
+terraform {
+  backend "azurerm" {
+    resource_group_name  = "my-resource-group"
+    storage_account_name = "myterraformstate"
+    container_name       = "tfstate"
+    key                  = "infrastructure.tfstate"
+  }
+}
+```
 ---
 
 ## 👥 Authors <a name="authors"></a>
 
-👤 **Your Name**
+👤 **Elio Cortés**
 
-- GitHub: [@yourhandle](https://github.com/yourhandle)
-- LinkedIn: [Your Profile](https://linkedin.com/in/yourhandle)
+- GitHub: [@NeckerFree](https://github.com/NeckerFree)
+- Twitter: [@ElioCortesM](https://twitter.com/ElioCortesM)
+- LinkedIn: [elionelsoncortes](https://www.linkedin.com/in/elionelsoncortes/)
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
 
@@ -196,21 +248,36 @@ If you like this project, please ⭐️ the repository and share it with others!
 
 ## 🙏 Acknowledgements <a name="acknowledgements"></a>
 
-- Microsoft Azure documentation
-- Ansible Azure Collection contributors
-- HashiCorp Terraform Modules
+- [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/)
+- [Ansible Azure Collection](https://galaxy.ansible.com/azure/azcollection) contributors
+- [HashiCorp Terraform Modules](https://registry.terraform.io/)
+- [devops-rampup](https://github.com/aljoveza/devops-rampup) — Backend & frontend prototype used as base for this project
+- [EPAM DevOps Campus](https://campus.epam.com/en/training) — Cloud and DevOps learning program
+- [ChatGPT](https://chatgpt.com/) — Assistance in automation, CI/CD, and documentation
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
 
 ---
 
 ## ❓ FAQ <a name="faq"></a>
 
-- **Can I deploy this to a different region?**
-  - Yes, update the `location` variable in Terraform and Ansible inventory.
+### 🔐 Where are secrets like passwords and keys stored?
+Secrets are securely stored as GitHub Actions secrets and injected at runtime into the workflows.
+
+### 🧪 Can I test changes before deploying to Azure?
+Yes! You can test locally using `terraform plan` and `ansible-playbook` in dry-run mode before committing changes.
+
+### 🌎 Where is the infrastructure deployed?
+By default, all resources are deployed to the `westus2` Azure region. You can change this in `infra/variables.tf`.
+
+### 🛠 What if I want to destroy all resources?
+You can run the `terraform-destroy.yml` GitHub Actions workflow to safely destroy the provisioned infrastructure.
+
+### 🐘 How is the database created?
+The Azure MySQL database is provisioned with Terraform and initialized using `movie_db.sql` from Ansible.
 
-- **What if I want to use a container instead of a VM for the API?**
-  - You can replace the VM setup with Azure Container Instances or Azure Kubernetes Service.
+### 🌐 What is the default URL for the frontend?
+The frontend is hosted on Azure Web App. The exact URL depends on the generated Azure App Service name. Check the Azure Portal or output logs.
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>