Thursday, August 15, 2024

Azure Windows VM Development and Web Server Setup

Steps to Launch a Windows VM, Connect to the VM, and Deploy a Web Server on Azure


1. Launching a Windows VM on Azure


1. Log in to the Azure Portal: Go to Azure Portal and log in with my account.

2. Create a Resource: Click the “+ Create a resource” button at the top of the screen.

3. Select Virtual Machine: Type “Virtual Machine” in the search bar and select “Virtual Machine.”

4. Enter Basic Settings:

Subscription: Select my Azure subscription.

Resource Group: Create a new resource group or select an existing one.

VM Name: Enter the name of the virtual machine.

Region: Choose the region where you want to deploy the VM.

Image: Select “Windows Server” (e.g., Windows Server 2019 Datacenter).

Size: Choose the VM size, e.g., Standard D2s v3.

Authentication Type: Select Password and set a username and password.

5. Configure Disks: Use the default settings or adjust as needed.

6. Networking Settings:

Virtual Network: Select the default virtual network or create a new one.

Subnet: Use the default subnet.

Public IP: Assign a public IP address.

Inbound Port Rules: Allow RDP (port 3389).

7. Review and Create: Review all the settings and click “Review + create,” then click “Create” to deploy the VM.


2. Connecting to the VM Using RDP


1. Check Public IP Address: After the VM is started, check the public IP address from the VM’s overview page in the Azure portal.

2. Download RDP File: Click the “Connect” button on the VM overview page and download the RDP file.

3. Run RDP App: Run the downloaded RDP file to start the RDP application.

4. Log in: When the RDP window appears, enter the username and password you set earlier and click “Connect.”


3. Deploying a Web Server via Server Manager


1. Open Server Manager: Once logged into the VM, Server Manager will open automatically. If not, open it from the Start menu.

2. Add Roles and Features: In Server Manager, click “Manage” and select “Add Roles and Features.”

3. Start the Wizard: On the “Before you begin” page, click “Next.”

4. Installation Type: Select “Role-based or feature-based installation” and click “Next.”

5. Server Selection: Ensure the current server is selected and click “Next.”

6. Select Server Roles: Choose “Web Server (IIS)” and, if prompted, click “Add Features.” Then click “Next.”

7. Features: Leave the default settings and click “Next.”

8. Web Server Role Services: Choose the necessary web server role services. You can leave the default settings and click “Next.”

9. Confirm Installation: Review the installation summary and click “Install.” Wait for the installation to complete.

10. Verify the Web Server: Once installed, click “Tools” in Server Manager and select “Internet Information Services (IIS) Manager” to verify that the web server is running.


4. Testing the Web Server


1. Test Locally: Open a web browser and enter http://localhost to check if the default IIS web page is displayed.

2. Test Remotely: Use the public IP address of the VM by entering http://<Public IP> in the browser to verify that the web page loads correctly.


This completes the process of launching a Windows VM on Azure, connecting to it via RDP, and deploying a web server using Server Manager.

Monday, August 12, 2024

Git project 1

 

Overview

Congratulations on starting your company's journey with Git and GitHub by open-sourcing the Shipping Cost Calculator Python script. All the developers have contributed to the repository, and their changes have been accepted and merged into a new global repository. Now, you have been asked to edit some of the code and also add few more files. For this, you will fork this repository, make the necessary edits, add files using Git CLI in the provided lab environment, and open a pull request.

Objectives

After completing this lab, you will be able to demonstrate that you can:

  1. Fork the upstream repository into your own account.
  2. Clone the code locally in the lab environment.
  3. Create a branch in the repository.
  4. Merge the branch back into the main branch.
  5. Create a pull request from the forked repository to the upstream repository.
  6. Revert a change that you made earlier.

Waviz Project: Building a Visualizer Without External Libraries

  Back in the day , music visualizers were magic. Whether it was the old Windows Media Player or Winamp, watching sound morph into motion fe...