DEV Community: ABITI KELECHI TAIWO

HOW TO PUSH CODE FROM A LOCAL REPOSITORY TO A REMOTE REPOSITORY LIKE GITHUB USING GIT BASH

ABITI KELECHI TAIWO — Fri, 12 Jul 2024 16:39:11 +0000

From you computer search pane, type git bash and launch it.
On the bash page start by running the command as in the pics below

click enter

click enter.

Explanation

git config: This is the command to configure Git settings.
--global: This option specifies that the configuration change should apply globally, meaning it will affect all Git repositories on your system.
user.name: This is the setting being configured, which specifies the author name used for commits.

When you run git config --global user.name , you're setting the author name for all future commits to . This information is stored in the Git configuration file (~/.gitconfig on Linux/macOS or %USERPROFILE%.gitconfig on Windows).

For example, running git config --global user.name "Kelechi Abiti" would set the author name to "Kelechi Abiti" for all future commits.

Note that you can also set the email address associated with your commits using git config --global user.email .

Setting your username and email address correctly is important because it helps identify you as the author of commits and allows others to contact you about your contributions to a project.
next command

mkdir lovely is a command to create a new directory (folder) named "lovely".

Here's a breakdown:

mkdir stands for "make directory" and is a command used to create new directories.
lovely is the name of the directory you want to create.

When you run mkdir lovely in your terminal or command prompt, it will create a new folder named "lovely" in your current working directory.

For example, if your current directory is /Users/yourname/Documents, running mkdir lovely would create a new folder at /Users/yourname/Documents/lovely.

The mkdir command is a fundamental command in computing, and it's used to create new directories to organize files and other directories.
next

cd stands for "change directory" and is a command used to navigate through the file system.
lovely is the name of the directory you want to switch to.

When you run cd lovely in your terminal or command prompt, it will change your current working directory to the "lovely" directory.

For example, if your current directory is /Users/yourname/Documents and you run cd lovely, your new current directory would become /Users/yourname/Documents/lovely.

The cd command is used to navigate through the file system, and it's essential for working with files and directories. Some other examples of cd usage include:

cd .. to move up one directory level
cd ~ to move to your home directory
cd / to move to the root directory

git init is a command used to initialize a new Git repository in the current directory.

When you run git init, Git sets up the necessary infrastructure to track changes and version your code. Here's what happens:

A new .git directory is created in the current directory. This directory contains all the metadata and version history for your repository.
A master branch is created, which will be the main branch for your repository.
Git sets up the basic configuration for the repository, including the default branch and remote tracking information.

By running git init, you're essentially telling Git to start paying attention to the files in your directory and prepare to track changes. This is the first step in creating a new Git repository.

Some key points to note:

git init only needs to be run once for a given directory.
It's usually run in the top-level directory of a project.
After running git init, you can start using other Git commands like git add, git commit, and git log to manage your code.

So, git init is the starting point for version control with Git!
next

touch index.html is a command used to create a new, empty file named "index.html" in the current directory.

Here's what happens:

touch is a command that creates a new file or updates the timestamp of an existing file.
index.html is the name of the file to be created.

When you run touch index.html, a new file named "index.html" is created in the current directory. The file is empty, meaning it contains no content.

The touch command is often used to:

Create a new file for editing or writing content
Update the timestamp of an existing file (e.g., to mark it as recently modified)
Create a placeholder file to reserve a filename

In the case of index.html, this file is often the main entry point for a website or web application, and it typically contains HTML content.

So, touch index.html is a quick way to create a new HTML file, ready for you to add content and build your web page!
next

vim is the command to launch the Vim text editor.
index.html is the name of the file to be opened.

When you run vim index.html, Vim will:

Open the file "index.html" in the current directory
Allow you to edit the file using Vim's commands and features
Display the file's contents in the terminal or command prompt

Vim is a highly configurable and feature-rich text editor that is popular among developers and power users. It has a steep learning curve, but offers:

Efficient editing capabilities
Customizable keyboard shortcuts
Advanced text manipulation features
Integration with other tools and plugins

By opening "index.html" in Vim, you can edit the file using Vim's unique keyboard-focused interface. If you're new to Vim, don't worry – you can always learn the basics and become a Vim master!

when the vim text editor is opened, you can open a different page and type www.chatgpt.com. when the page opens, search for a sample html resume for a particular designation of your choice.

copy and paste the sample resume in the editor page, hit the "I" button on your keyboard to be able to insert and make changes in the html file.
Aftermaking the changes, hit the escape button, then hold the shift and; key the type wq and enter and it will take you to the bash page.

git add index.html is a command that stages the file "index.html" for the next commit.

Here's what happens:

git add is the command to stage changes for the next commit.
index.html is the name of the file to be staged.

When you run git add index.html, Git:

Adds the latest changes made to "index.html" to the staging area (also known as the index).
Prepares the file to be committed in the next git commit command.
Snapshots the current state of the file, ready to be committed.

The staging area is like a holding area where you prepare changes before committing them. By staging a file, you're telling Git that you want to include those changes in your next commit.

Think of it like preparing a package to be shipped:

git add is like putting the file in a box (staging area).
git commit is like shipping the box (committing the changes).

By staging "index.html", you're preparing it to be committed, making it a part of your project's version history.

git commit -m "my first commit" is a command that commits the changes you've staged, with a meaningful message to describe the commit.

Here's what happens:

git commit is the command to commit the changes in the staging area.
-m is an option to specify a commit message.
"my first commit" is the commit message, enclosed in quotes.

When you run git commit -m "my first commit", Git:

Takes a snapshot of the changes in the staging area.
Creates a new commit with the changes.
Assigns the commit message "my first commit" to the commit.
Updates the branch (e.g., master) to point to the new commit.

The commit message is important, as it provides a brief description of the changes made in the commit. This helps you (and others) understand the history of the project and what changes were made at each step.

By committing with a meaningful message, you're:

Documenting your progress
Making it easier to understand the project's history
Creating a reference point for future changes

Congratulations, you've just made your first commit!
next
go to www.github.com, click create a new repository, type the repository name, check public,check add a README file and click create repository.

click on the created repository, g
click on code and copy the link from the HTTP

Goto git bash page and type the command
git remote add origin and paste the link you copied from github

git remote add origin is a command that adds a remote repository to your local Git repository, named "origin", and specifies its URL.

Here's what happens:

git remote add is the command to add a remote repository.
origin is the name given to the remote repository (a common convention).
is the URL of the remote repository, such as a GitHub or GitLab repository.

When you run git remote add origin , Git:

Creates a new remote repository reference named "origin".
Associates the URL with the remote repository.
Allows you to push (upload) your local changes to the remote repository.
Allows you to pull (download) changes from the remote repository.

By adding a remote repository, you're connecting your local repository to a central location where collaborators can access and share code. This enables you to:

Push your changes to share with others.
Pull changes from others to stay up-to-date.
Collaborate on the same project.

The "origin" name is a common convention, but you can use any name you like. The URL should point to the remote repository you want to connect to.

Now, you're ready to push your changes to the remote repository and collaborate with others!
next

git push origin master is a command that uploads your local changes from the "master" branch to the remote repository named "origin".

Here's what happens:

git push is the command to upload changes to a remote repository.
origin is the name of the remote repository (added earlier with git remote add).
master is the branch you're pushing changes from (usually the main branch).

When you run git push origin master, Git:

Packs your local changes into a bundle.
Uploads the changes to the remote repository ("origin").
Updates the remote "master" branch with your local changes.
Makes your changes visible to others who pull from the remote repository.

By pushing your changes, you're:

Sharing your work with collaborators.
Updating the central repository with your latest changes.
Making your changes available for others to pull and use.

Remember, git push only uploads changes committed locally (with git commit). If you've made changes but haven't committed them, you'll need to commit and then push.

Now, your changes are live in the remote repository, and others can access them!
next
goto github repository page you copied the link from, click on settings,from the left hand side, click pages, change the branch to master and save.
wait for a pop up to tell you that you are life at a particular link.
copy the link, put it in the search area of your browser, hit enter and walaaa!! see you have push your resume to a git and is live.

PROVIDE A SHARED SERVICES HUB VIRTUAL NETWORK WITH ISOLATION AND SEGMENTATION

ABITI KELECHI TAIWO — Fri, 12 Jul 2024 12:13:59 +0000

Open a browser and navigate to the Azure portal and login.
To create a Virtual Network, in the search bar at the top of the portal type “Virtual Networks” and select “Virtual Networks” from the results.
In the “Virtual Networks” portal pane, select ““+ Create”.

Fill out all the tabs of the creation process by using the values in the following table:

Resource group: RG1
Name: app-vnet
Region: East US
IPv4 address space: 10.1.0.0/16
Subnet name: frontend
Subnet address range: 10.1.0.0/24
Subnet name: backend
Subnet address range: 10.1.1.0/24
Note: Leave all other settings as their defaults. Select “Next” to advance to the next tab, and Create to create the virtual network.

Following the same steps as above, create the Azure virtual network Hub-vnet by using the values in the following table:

Resource group: RG1
Name: Hub-vnet
Region: East US
IPv4 address space: 10.0.0.0/16
Subnet name: AzureFirewallSubnet
Subnet address range: 10.0.0.0/24

Once the deployment is complete. Navigate back to the portal, in the search bar type “resource groups” and select Resource Groups” from the results. Select on “RG1” in the main pane and comfirm both virtual networks have been deployed.

SETUP A PEER RELATIONSHIP BETWEEN THE VIRTUAL NETWORKS:
Setting up a peer relationship between the two virtual networks will allow traffic to flow in both directions between the app-vnet and hub-vnet virtual networks.
In the Portal in the RG1 resource group view. Select on the “app-vnet” virtual network.
On the app-vnet context menu on the left hand side of the portal scroll down and select on peerings
In the app-vnet peerings pane, Select + Add.

Fill out the form using the values in the following table:

This virtual network Peering link name: app-vnet-to-hub
Remote virtual network Peering link name: hub-to-app-vnet
Virtual network: hub-vnet

Note: Leave all other settings as their defaults. Select “Add” to create the virtual network peering.

Once the process completes, and after the configuration updates. Validate that the Peering status is set to Connected. (you may have to refresh the page to see the updated status).

STORAGE FOR INTERNAL COMPANY DOCUMENTS

ABITI KELECHI TAIWO — Fri, 24 May 2024 13:41:04 +0000

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

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.

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.

To test and ensure the file isn't accessible (Private)
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.

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.

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.

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. Refer back to Lab 02a if you need detailed instructions.
Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.

HOW TO PROVIDE STORAGE FOR A PUBLIC WEBSITE

ABITI KELECHI TAIWO — Fri, 24 May 2024 10:43:44 +0000

Click on the +create button to navigate to the storage account creation page.
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.

In the storage account, in the Data management section, select the Redundancy blade.
Ensure Read-access Geo-redundant storage is selected.

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

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.

click on + container and name your container and click the create button to create your Storage container.

container created.

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

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

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.

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.

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.

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.
Notice your options to keep all versions or delete versions after.
Don’t forget to Save your changes.

Upload another version of your container file. This overwrites your existing file.
Your previous file version is listed on Show deleted blobs page.

STORAGE CREATION FOR THE IT DEPARTMENT TESTING AND TRAINING

ABITI KELECHI TAIWO — Wed, 22 May 2024 15:55:56 +0000

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.

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.
Nb: The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired.

In the Settings section, select the Configuration blade.
Ensure Secure transfer required is Enabled.
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.

Until the storage is needed again, disable requests to the storage account. Learn more about disabling shared keys.
In the Settings section, select the Configuration blade.
Ensure Allow storage account key access is Disabled.
Be sure to Save your changes.

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.

DEPLOYING A WINDOWS 11 VIRTUAL MACHINE THAT IS HIGHLY AVAILABLE

ABITI KELECHI TAIWO — Mon, 20 May 2024 15:37:11 +0000

When you log in to your Azure, at the task bar, type virtual machine and click on the one that is greyed out.
to create a virtual machine, click on the + create as shown below and select the Azure virtual machine create a virtual machine hosted by Azure and wait.

It takes you to the Create a Virtual Machine Page where you have your basics Tab. This comprises of your Project Detail which includes your subscription and resource group. click on the create resource group and name it. see diagram below.

Go to your instant details tab,name your virtual machine, chose your region and the availability zone as shown below.

NB: I chose Three availability zones in order have my data replicated in those three zones so that I can easily recover my data from other zones in case any of the zones fail.

Because I am deploying a windows 11 virtual machine, at the image section I selected windows 11 pro as shown below and leave the others as default.

For the administrator account section, we create the user name and password which you will use to log into the virtual machine after creation.we create as shown below

next is the Inbound Port Rules. leave the allowed selected ports checked and because we are deploying a windows machine, we select RDP 3389 for the selected inbound ports as shown below
NB: the ports are be checked in other to have a synergy with whatever am going to need it for. without it, it is deactivated.

For the licensing section, check it as shown below.

For the monitoring Section, we disable the diagnostics so to protect my work because of defense in-depth which is a strategy that leverages multiple security measures to protect an organization's assets. see below for disabling diagnostics.

For the tagging Section, we use it to tie the cost of running the machine to the department that uses it. so we tag as shown below

after which we click review and create and allow it to load for a while. If the validation check is green, then we are good to go, but if red, the we need to check some things we did wrongly while setting up the VM and correct them. the validation check will indicate as shown below.

Notice that the cost was tied to the IT department. see below.

Click on the Create button to create our Virtual machine and allow it to load. It displays deployment in progress as shown below

And after a while it displays your deployment is complete as shown below.

click go to resource button as indicated above and it takes you to the VM page where you will see the status indicating running, and the public IP address displayed as shown below

Click on the IP adress and it brings you to the time out page. stretch out the time out from 4mins to 30mins and save. as shown below

Reason: If the time out is not reset to max time which is 30 minutes, you might be timed out while working on the VM.
when it pops out saved public IP address changes and checked green, close that saved time out window to bring you back to our VM page as shown below. Click on connect to connect to your virtual machine as indicated below.

.
After loading, it brings you to the native RDP page where you will click on select as shown

At the right hand side of the screen is the native RDP trying to configure the prerequisites and the public IP to validate. see pics below.

After configuration, the validating changes to configured as show below

Next click on the Download RDP File as shown below

After downloading, Since we are configuring windows machine, we click on the downloaded RDP File and it will start connecting. For windows user, it connects directly, but MAC users, you need to download a Microsoft remote desktop in other to open the downloaded file. so when we click on the downloaded file, it brings us to a page where you need to log in with the password you created in the admin while displaying your username. as shown below.

Log in the password and click continue, allow it to load for a while and a windows 11 Interface displays as shown below

allows it to load and it displays what you see below which is normal.

Click on the next button and a windows 11 computer desktop displays as below.

FACTORS TO CONSIDER WHEN SELECTING A REGION

ABITI KELECHI TAIWO — Mon, 13 May 2024 10:32:45 +0000

Proximity to Users: consideration to the nearness of consumers will improve application performance and reduce customers latency.
Region Cost consideration: considering our budget plans in regards to region chosen is necessary as regions may have varying price structures.
Service availability: note: not all services are available in all regions perhaps because of compliance reasons or some other similar reasons
Cost : In Azure, cost of services and Storage is pay-As-you-Go and varies between regions. so to ensure we don't spend more than we earn, costing is considered
Network Performance: performance of our applications and services may depends on the network performance in a specific area. so Azure gives us the option to chose any region with incredibly high network performance
Latency: This is the shortest time it takes to make a request and have it answered. this is because of the proximity of your regions, availability zones, network quality and data transfer methods.
Disaster recovery and business continuity: Without this in consideration, company can experience data loss, reduced productivity, damaged reputation and out of budget expenses. so we can chose a region that satisfies our needs from various data recovery.
Performance: this can affect our applications and services if wrongly selected. so options ore available to select a region that has high performance capabilities.
Customer Support: the level of customer support may vary within regions as their services can be through chats, phone calls and emails. to ensure we get we need we may consider the regions that has good customer support to ensure we are getting the help we need.

Important Cloud Computing Concepts

ABITI KELECHI TAIWO — Fri, 10 May 2024 14:03:52 +0000

1.Virtualization : This is a technology that is used to create the similar representations of storage, servers, networks etc but in virtual forms. Virtual software mimic the true functions of the physical devices and can run multiple virtual machines on a single physical machine.

2.Scalability:This is the ability to handle a great amount of work. The system has the ability to adjust itself to when there are much traffics to contain the number of traffics and readjusts whenever the traffic reduces.

3.Agility: This is the the ability to respond quickly develop, test or launch applications quickly to attain fast service for business growth.

4.High Availability: This is the ability of a system to operate without interruption or failing over time even when some of its components are down

5.Fault tolerance: This is the ability of a system to continue operating uninterruptedly even though there are failures of some of its component. this is because there are replications of any data stored in the cloud to other data centers. so if one data center malfunctions the other compensates for it.

6.Global Reach: This means that cloud services can be accessed from anywhere around the globe because they have more data center and regions more than any other cloud providers.

Difference Between Scalability and Elasticity.
7.Scalability has to do with Long term strategy to ensure that the technology deployed for the business grows as the business grows. It has the ability to scale itself to handle any load given to it where as elasticity is a short term method of handling sudden or abrupt changes without failing.