DEV Community: Wisdom Benson

How to push your files from your local environment to Github

Wisdom Benson — Wed, 20 Nov 2024 18:19:04 +0000

• In this tutorial, I will be teaching you how to:

Download Git

Configure your git

Work with the configured environment

Clone your github repo.

Push to Github

Let's begin.

Step 1: Download Git

Use this link - (https://git-scm.com/downloads) to download Git.

Step 2: Configure your git

Give your Git a Name & Email.

Step 3: Work with the Git environment.

• Make a directory & change the directory to what you created (Give it any name)

• Initialize a git branch

• Create a file

• Add contents to the file you just created

Step 4: Clone your github repo

• Sign in to your github & create a new repository

• Copy your repository code

• Clone the repository to your git

Step 5: Push your File to Git

• Commit the Git (You can also add a message to the commit by inputting '-m' then the message)

• Now push your file to Github. NB: You will be asked to login your github acct to authorize access.

• Your File has been successfully pushed to Github

Get your file link from Github & View your code on a browser

• If you don't see the link immediately after saving, refresh the browser

Congratulations on pushing your Git File to Github 🎉

Creating a Linux VM and installing nginx on it

Wisdom Benson — Tue, 19 Nov 2024 21:03:09 +0000

Step-by-Step Guide to Creating a Linux VM and installing nginx on it

Step 1: Search & Select Virtual Machine on Azure Portal.

Step 2: Select Create + and click on Azure Virtual Machines.

Step 3: For Resource Group select Create New, Give your resource group a name and click on OK to save changes.

Step 4: Provide a Virtual Machine name. Ensure the name is unique and meets the naming requirements.

Step 5: Select Images & Choose Ubuntu Server 20.04.

Step 6: Go to the Administrator Account and Create a Username & Password.

Step 7: In the Inbound port roles, select HTTP & SSH.

Step 8: Go to Monitoring, Disable Boot Diagnostics.

Step 9: Click on the “Review + Create” button. If the validation passes, the deployment will proceed. If not, note any recommendations, fix them, and try again. Deployment might take 3-5 minutes.

Step 10: Once the VM is deployed, find its Public IP Address in the Overview tab.

Step 11: Open a terminal(like Windows Powershell or use an SSH client like PuTTY) and connect to your VM using SSH

• Replace and with your VM's details.
• Enter yes and then your password (not visible while typing in Linux).
• Make sure that you are logged in as root use the command - sudo su.

Step 12: Once connected, run the following commands to ensure the package list is to up-to-date.

• apt update

Step 13: Install nginx on a Linux Server

• Type the command $ apt install nginx.
apt(Is the package manager of nginx)
install(This is a verb and the action that you want the package manager to perform), nginx (This is what you want to install on the VM).

Step 14: Test Nginx Installation
• We can verify the installation by pasting the IP Address of the VM in a browser.

By following these steps, you've successfully created a Linux VM in Azure and installed Nginx. This setup is ready to serve web traffic and can be scaled based on your requirements. You can now begin deploying web applications customizing NGINX as needed

Create a Windows 11 VM that is highly available

Wisdom Benson — Tue, 19 Nov 2024 17:42:03 +0000

Step-by-Step Guide to create a Windows 11 VM on Azure that is highly available

Create a Virtual Machine

Step 1: Search for and select Virtual Machine on Azure portal.

Step 2: Select Create + and click on Azure Virtual Machines.

Step 3: For Resource Group select Create New, Give your resource group a name and click on OK to save changes.

Step 4: Provide a Virtual Machine name. Ensure the name is unique and meets the naming requirements.

Step 5: Choose at least 2 availability zones.

Step 6: Select Images & Choose Windows 11 VM.

Step 7: Go to the Administrator Account and Create a Username & Password.

Step 8: In the Inbound port roles, select HTTP & RDP.

Step 9: Go to Monitoring, Disable Boot Diagnostics.

Step 10: Check Licensing, : By default, this is unchecked. Click the box to check it.

Step 11: Click on the “Review + Create” button. If the validation passes, the deployment will proceed. If not, note any recommendations, fix them, and try again. Deployment might take 3-5 minutes.

Step 12: Once the virtual machine is deployed, click on the “Connect” button in the virtual machine blade in the Azure portal.

Step 13: Click “Native RDP”, select, and wait for the configured sign to be displayed on the right-hand side. Download the RDP file.

Step 14: Open the RDP file from your local computer and click on “Connect”. Enter the admin details created during the VM setup.

Step 15: Follow the prompt and click “Continue”. Use the username and password created for the admin section.

With this steps you will be able to create a Virtual Machine.

Provide storage for a new company app

Wisdom Benson — Fri, 15 Nov 2024 01:13:47 +0000

Create the storage account and managed identity

1. Provide a storage account for the web app.

In the portal, search for and select Storage accounts.

Select + Create.

For Resource group select Create new. Give your resource group a name and select OK to save your changes.

Provide a Storage account name. Ensure the name is unique and meets the naming requirements.

Move to the Encryption tab.

Check the box for Enable infrastructure encryption.

Notice the warning, This option cannot be changed after this storage account is created.

Select Review + Create.

Wait for the resource to deploy.

2. Provide a managed identity for the web app to use.

Search for and select Managed identities.

Select Create.

Select your resource group.

Give your managed identity a name.

Select Review and create, and then Create.

3. Assign the correct permissions to the managed identity. The identity only needs to read and list containers and blobs.

Search for and select your storage account.

Select the Access Control (IAM) blade.

Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Storage Blob Data Reader role.

On the Members page, select Managed identity.

Select Select members, in the Managed identity drop-down select User-assigned managed identity.

Select the managed identity you created in the previous step.

Click Select and then Review + assign the role.

Select Review + assign a second time to add the role assignment.

Your storage account can now be accessed by a managed identity with the Storage Data Blob Reader permissions.

Secure access to the storage account with a key vault and key

1. To create the key vault and key needed for this part of the lab, your user account must have Key Vault Administrator permissions.

In the portal, search for and select Resource groups.

Select your resource group, and then the Access Control (IAM) blade.

Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Key Vault Administrator role.

On the Members page, select User, group, or service principal.

Select Select members.

Search for and select your user account. Your user account is shown in the top right of the portal.

Click Select and then Review + assign.

Select Review + assign a second time to add the role assignment.

You are now ready to continue with the lab.

2. Create a key vault to store the access keys.

In the portal, search for and select Key vaults.

Select Create.

Select your resource group.

Provide the name for the key vault. The name must be unique.

Ensure on the Access configuration tab that Azure role-based access control (recommended) is selected.

Select Review + create.

Wait for the validation checks to complete and then select Create.

After the deployment, select Go to resource.

On the Overview blade ensure both Soft-delete and Purge protection are enabled.

3. Create a customer-managed key in the key vault.

In your key vault, in the Objects section, select the Keys blade.

Select Generate/Import and Name the key.

Take the defaults for the rest of the parameters, and Create the key.

Configure the storage account to use the customer managed key in the key vault

1. Before you can complete the next steps, you must assign the Key Vault Crypto Service Encryption User role to the managed identity.

In the portal, search for and select Resource groups.

Select your resource group, and then the Access Control (IAM) blade.

Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Key Vault Crypto Service Encryption User role.

On the Members page, select Managed identity.

Select Select members, in the Managed identity drop-down select User-assigned managed identity.

Select your managed identity.

Click Select and then Review + assign.

Select Review + assign a second time to add the role assignment.

2. Configure the storage account to use the customer managed key in your key vault.

Return to your the storage account.

In the Security + networking section, select the Encryption blade.

Select Customer-managed keys.

Select a key vault and key. Select your key vault and key.

Select to confirm your choices.

Ensure the Identity type is User-assigned.

Select an identity.

Select your managed identity then select Add.

Save your changes.

If you receive an error that your identity does not have the correct permissions, wait a minute and try again.

Configure an time-based retention policy and an encryption scope.

1. The developers require a storage container where files can’t be modified, even by the administrator.

Navigate to your storage account.

In the Data storage section, select the Containers blade.

Create a container called hold. Take the defaults. Be sure to Create the container.

Upload a file to the container.

In the Settings section, select the Access policy blade.

In the Immutable blob storage section, select + Add policy.

For the Policy type, select time-based retention.

Set the Retention period to 5 days.

Be sure to Save your changes.

Try to delete the file in the container.

Verify you are notified failed to delete blobs due to policy.

2. The developers require an encryption scope that enables infrastructure encryption.

Navigate back to your storage account.

In the Security + networking blade, select Encryption.

In the Encryption scopes tab, select Add.

Give your encryption scope a name.

The Encryption type is Microsoft-managed key.

Set Infrastructure encryption to Enable.

Create the encryption scope.

Return to your storage account and create a new container.

Notice on the New container page, there is the Name and Public access level.

Notice in the Advanced section you can select the Encryption scope you created and apply it to all blobs in the container.

Provide shared file storage for the company offices

Wisdom Benson — Sun, 10 Nov 2024 09:48:09 +0000

Create and configure a storage account for Azure Files.

1. Create a storage account for the finance department’s shared files.

In the portal, search for and select Storage accounts.

Select + Create.

For Resource group select Create new. Give your resource group a name and select OK to save your changes.

Provide a Storage account name. Ensure the name meets the naming requirements.

Set the Performance to Premium.

Set the Premium account type to File shares.

Set the Redundancy to Zone-redundant storage.

Select Review and then Create the storage account.

Wait for the resource to deploy.

Select Go to resource.

Create and configure a file share with directory.

1. Create a file share for the corporate office.

In the storage account, in the Data storage section, select the File shares blade.

Select + File share and provide a Name.

Review the other options, but take the defaults.

Select Create.

2.Add a directory to the file share for the finance department. For future testing, upload a file.

Select your file share and select + Add directory.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xfg1ihu9abgkkqc0lhvq.png

Name the new directory finance.

Select Browse and then select the finance directory.
Notice you can Add directory to further organize your file share.

Upload a file of your choosing.

Configure and test snapshots.

Similar to blob storage, you need to protect against accidental deletion of files. You decide to use snapshots.

Select your file share.

In the Operations section, select the Snapshots blade.

Select + Add snapshot. The comment is optional. Select OK.

Select your snapshot and verify your file directory and uploaded file are included.

2. Practice using snapshots to restore a file

Return to your file share.

Browse to your file directory.

Locate your uploaded file and in the Properties pane select Delete.

Select Yes to confirm the deletion.

Select the Snapshots blade and then select your snapshot.

Navigate to the file you want to restore,

Select the file and the select Restore.

Provide a Restored file name.

Verify your file directory has the restored file.

Configure restricting storage access to selected virtual networks.

1. This tasks in this section require a virtual network with subnet. In a production environment these resources would already be created.

Search for and select Virtual networks.

Select Create. Select your resource group. and give the virtual network a name.

Take the defaults for other parameters, select Review + create, and then Create.

Wait for the resource to deploy.

Select Go to resource.

In the Settings section, select the Subnets blade.

Select the default subnet.

In the Service endpoints section choose Microsoft.Storage in the Services drop-down.

Do not make any other changes.

Be sure to Save your changes.

2. The storage account should only be accessed from the virtual network you just created.

Return to your files storage account.

In the Security + networking section, select the Networking blade.

Change the Public network access to Enabled from selected virtual networks and IP addresses.

In the Virtual networks section, select Add existing virtual network.

Select your virtual network and subnet, select Add.

Be sure to Save your changes.

Select the Storage browser and navigate to your file share.
Verify the message not authorized to perform this operation. You are not connecting from the virtual network.

Provide private storage for internal company documents

Wisdom Benson — Fri, 08 Nov 2024 23:50:25 +0000

Create a storage account and configure high availability.

1. Create a storage account for the internal private company documents.

In the portal, search for and select Storage accounts.

Select + Create.

Select the Resource group created in the previous lab.

Set the Storage account name to private. Add an identifier to the name to ensure the name is unique.

Select Review, and then Create the storage account.

Wait for the storage account to deploy, and then select Go to resource.

2. This storage requires high availability if there’s a regional outage. Read access in the secondary region is not required. Configure the appropriate level of redundancy.

In the storage account, in the Data management section, select the
Redundancy blade.

Ensure Geo-redundant storage (GRS) is selected.

Refresh the page.

Review the primary and secondary location information.

Save your changes.

Create a storage container, upload a file, and restrict access to the file.

1. Create a private storage container for the corporate data.

In the storage account, in the Data storage section, select the Containers blade.

Select + Container.

Ensure the Name of the container is private.

Ensure the Public access level is Private (no anonymous access).

As you have time, review the Advanced settings, but take the defaults.

Select Create.

2. For testing, upload a file to the private container. the type of file doesn’t matter. A small image or text file is a good choice. Test to ensure the file isn’t publically accessible.

Select the container.

Select Upload.

Browse to files and select a file.

Upload the file.

Select the uploaded file.

On the Overview tab, copy the URL.

Paste the URL into a new browser tab.

Verify the file doesn’t display and you receive an error.

*3. An external partner requires read and write access to the file for at least the next 24 hours. Configure and test a shared access signature (SAS). *

Select your uploaded blob file and move to the Generate SAS tab.

In the Permissions drop-down, ensure the partner has only Read permissions.

Verify the Start and expiry date/time is for the next 24 hours.

Select Generate SAS token and URL.

Copy the Blob SAS URL to a new browser tab.

Verify you can access the file. If you have uploaded an image file it will display in the browser. Other file types will be downloaded.

Configure storage access tiers and content replication.

1. To save on costs, after 30 days, move blobs from the hot tier to the cool tier.

Return to the storage account.

In the Overview section, notice the Default access tier is set to Hot.

In the Data management section, select the Lifecycle management blade.

Select Add rule.

Set the Rule name to movetocool.

Set the Rule scope to Apply rule to all blobs in the storage account.

Select Next.

Ensure Last modified is selected.

Set More than (days ago) to 30.

In the Then drop-down select Move to cool storage.

As you have time, review other lifecycle options in the drop-down.
Add the rule.

2. The public website files need to be backed up to another storage account.

In your storage account, create a new container called backup. Use the default values.

Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.

In the Data management section, select the Object replication blade.

Select Create replication rules.

Set the Destination storage account to the private storage account.

Set the Source container to public and the Destination container to backup.

Create the replication rule.

Optionally, as you have time, upload a file to the public container.
Return to the private storage account and refresh the backup container. Within a few minutes your public website file will appear in the backup folder.

Provide storage for the public website

Wisdom Benson — Thu, 07 Nov 2024 03:42:43 +0000

Create a storage account with high availability.

1. Create a storage account to support the public website.

In the portal, search for and select Storage accounts.

Select + Create.

For resource group select new. Give your resource group a name and select OK.

Set the Storage account name to publicwebsite. Make sure the storage account name is unique by adding an identifier.

Take the defaults for other settings.

Select Review and then Create.

Wait for the storage account to deploy, and then select Go to resource.

2. This storage requires high availability if there’s a regional outage. Additionally, enable read access to the secondary region

In the storage account, in the Data management section, select the Redundancy blade.

Ensure Read-access Geo-redundant storage is selected.

Review the primary and secondary location information.

3. Information on the public website should be accessible without requiring customers to login.

In the storage account, in the Settings section, select the Configuration blade.

Ensure the Allow blob anonymous access setting is Enabled.

Be sure to Save your changes.

Create a blob storage container with anonymous read access

1. The public website has various images and documents. Create a blob storage container for the content.

In your storage account, in the Data storage section, select the Containers blade.

Select + Container.

Ensure the Name of the container is public.

Select Create.

2. Customers should be able to view the images without being authenticated. Configure anonymous read access for the public container blobs.

Select your public container.

On the Overview blade, select Change access level.

Ensure the Public access level is Blob (anonymous read access for blobs only).

Select OK.

Practice uploading files and testing access.

1. For testing, upload a file to the public container. The type of file doesn’t matter. A small image or text file is a good choice.

Ensure you are viewing your container.

Select Upload.

Browse to files and select a file. Browse to a file of your choice.

Select Upload.

Close the upload window, Refresh the page and ensure your file was uploaded.

2. Determine the URL for your uploaded file. Open a browser and test the URL.

Select your uploaded file.

On the Overview tab, copy the URL.

Paste the URL into a new browser tab.

If you have uploaded an image file it will display in the browser. Other file types should be downloaded.

Configure soft delete

1. It’s important that the website documents can be restored if they’re deleted. Configure blob soft delete for 21 days.

Go to the Overview blade of the storage account.

On the Properties page, locate the Blob service section.

Select the Blob soft delete setting.

Ensure the Enable soft delete for blobs is checked.

Change the Keep deleted blobs for (in days setting is 21.

Notice you can also Enable soft delete for containers.

Don’t forget to Save your changes.

2. If something gets deleted, you need to practice using soft delete to restore the files.

Navigate to your container where you uploaded a file.

Select the file you uploaded and then select Delete.

Select OK to confirm deleting the file.

On the container Overview page, toggle the slider Show deleted blobs. This toggle is to the right of the search box.

Select your deleted file, and use the ellipses on the far right, to Undelete the file.

Refresh the container and confirm the file has been restored.

Configure blob versioning

1. It’s important to keep track of the different website product document versions.

Go to the Overview blade of the storage account.

In the Properties section, locate the Blob service section.

Select the Versioning setting.

Ensure the Enable versioning for blobs checkbox is checked.

Don’t forget to Save your changes.

2. As you have time experiment with restoring previous blob versions.

Upload another version of your container file. This overwrites your existing file.

Your previous file version is listed on Show deleted blobs page.

Provide storage for the IT department testing and training

Wisdom Benson — Tue, 05 Nov 2024 12:29:57 +0000

Create a resource group and a storage account.

1. Create and deploy a resource group to hold all your project resources.

In the Azure portal, search for and select Resource groups.

Select + Create.

Give your resource group a name. For example, storagerg.

Select a region. Use this region throughout the project.

Select Review and create to validate the resource group.

Select Create to deploy the resource group.

2. Create and deploy a storage account to support testing and training.

In the Azure portal, search for and select Storage accounts.

Select + Create.

On the Basics tab, select your Resource group.

Provide a Storage account name. The storage account name must be unique in Azure.

Set the Performance to Standard.

Select Review, and then Create.

Wait for the storage account to deploy and then Go to resource.

Configure simple settings in the storage account.

1. The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired.

In your storage account, in the Data management section, select the Redundancy blade.

Select Locally-redundant storage (LRS) in the Redundancy drop-down.

Be sure to Save your changes.

Refresh the page and notice the content only exists in the primary location.

2. The storage account should only accept requests from secure connections.

In the Settings section, select the Configuration blade.

Ensure Secure transfer required is Enabled.

3. Developers would like the storage account to use at least TLS version 1.2.

In the Settings section, select the Configuration blade.

Ensure the Minimal TLS version is set to Version 1.2.

4. Until the storage is needed again, disable requests to the storage account.

In the Settings section, select the Configuration blade.

Ensure Allow storage account key access is Disabled.

Be sure to Save your changes.

5. Ensure the storage account allows public access from all networks

In the Security + networking section, select the Networking blade.

Ensure Public network access is set to Enabled from all networks.

Be sure to Save your changes.