Before diving headfirst into advanced DevOps concepts like automation and infrastructure, I needed to get my base environment in order. I already have a solid background in web development, with several ongoing projects hosted on GitHub. My immediate goal was simple: reconnect my newly formatted laptop to those existing repositories so I could keep pushing updates directly to them without creating redundant, duplicated repositories.

If you ever format your computer or switch to a new machine, here is the complete, step-by-step breakdown of how to restore access using SSH authentication, alongside a few command-line lessons I learned along the way.

Step 1: Installing Git & The Linux Terminal Environment

Instead of using a default package manager, I downloaded and installed Git directly from the official website (git-scm.com).

Why this matters: On a Windows computer, installing "Git for Windows" includes a tool called Git Bash. Git Bash gives you a Linux-like terminal emulator right inside Windows. This serves as a great bridge when transitioning into DevOps, allowing you to run actual Linux and Bash commands natively without setting up a heavy virtual machine.

Step 2: Configuring Your Identity

Git needs to know who is authoring the code changes. You must set your global username and email address in your terminal.

git config --global user.name "Your Name"
git config --global user.email "your-email@example.com"

Important Detail: Replace "Your Name" with your actual name and "your-email@example.com" with the exact email address linked to your GitHub account. If you make a typo in your email here, Git will still record your work, but GitHub will fail to link those commits to your profile, meaning you won't get credit on your contribution graph.

Step 3: Generating an SSH Key (The Digital Handshake)

GitHub no longer allows you to type your account password into the terminal to upload code. Instead, you generate a secure digital key on your computer.

Run this command in your terminal (using your own GitHub email address):

ssh-keygen -t ed25519 -C "your-email@example.com"

When prompted where to save the key, press Enter three times to accept the default settings.

Why this matters: ed25519 is a modern, highly secure algorithm for SSH keys. The email address at the end of this command is simply a text label so you can identify the key later; GitHub does not use it to authenticate you.

Step 4: Adding the Key to Your GitHub Account

Now you need to copy the public key generated by your computer and give it to GitHub.

First, print the key to your terminal screen:

cat ~/.ssh/id_ed25519.pub

Highlight and copy the entire line of text that appears. Then:

1. Log into GitHub in your web browser.

2. Click your profile picture in the top right corner and select Settings.

3. Go to SSH and GPG keys and click New SSH key.

4. Give it a title (like "Personal Laptop") and select Authentication Key from the Key Type dropdown.

5. Paste your copied text into the box and click Add SSH key.

Why choose Authentication Key over Signing Key?

• An Authentication Key acts as your secure password to download (git pull) and upload (git push) code.

• A Signing Key is an advanced feature used to put a cryptographic seal on commits to prove they weren't altered. For reconnecting your workspace, you need an Authentication Key.

Step 5: Testing Your Connection

Before trying to download any code, verify that your laptop and GitHub can talk to each other securely:

ssh -T git@github.com

If everything is configured correctly, GitHub will reply directly in your terminal:

"Hi your-username! You've successfully authenticated, but GitHub does not provide shell access."

Step 6: Cloning Your Existing Repositories

Now you can bring your existing web development projects back onto your computer without creating new repositories.

1. Go to your repository on GitHub.

2. Click the green Code button.

3. Select the SSH tab (do not choose HTTPS) and copy the link.

4. Open your terminal, navigate to where you store your work (like your Desktop), and run:

git clone git@github.com:your-username/your-repository-name.git

Once the download finishes, move inside the project folder:

cd your-repository-name

code . 

You are now right back where you left off! You can edit your HTML, CSS, or JavaScript files, and push updates directly to the exact same GitHub repository using git add, git commit, and git push.

Real-World Terminal Lessons Learned

When working in a terminal, syntax is strictly enforced. Here are two real errors I hit during this setup process and why they happened:

1. 'clonegit' is not a git command: This happens if you forget the space between git clone and the link (git clonegit@github...). In command-line interfaces, spaces are mandatory because they tell the computer where the action ends and the target begins.

2. bash: cd: Desktop: No such file or directory: If your terminal path already shows ~/Desktop, you are already sitting on the Desktop. Trying to run cd Desktop tells the system to look for a second folder named "Desktop" inside your current Desktop.

Setting up your environment correctly from the ground up gives you a solid base. With your existing web projects reconnected, you can build new features, commit changes cleanly, and focus on expanding into DevOps with confidence.