Rhobincu: /* Part 1: Secure Authentication (SSH Keys) */

2026-02-23T00:41:41Z

Part 1: Secure Authentication (SSH Keys)

Rhobincu la 23 februarie 2026 00:40

2026-02-23T00:40:39Z

Rhobincu la 23 februarie 2026 00:39

2026-02-23T00:39:55Z

Afișare diferențe

Rhobincu: Pagină nouă: = Lab 1: Foundation of Process - Git and GitLab Basics = == Introduction == Welcome to the first lab of Software Development Process and Testing (SDPT). In our lecture, we discuss...

2026-02-23T00:34:29Z

Pagină nouă: = Lab 1: Foundation of Process - Git and GitLab Basics = == Introduction == Welcome to the first lab of Software Development Process and Testing (SDPT). In our lecture, we discuss...

Pagină nouă

= Lab 1: Foundation of Process - Git and GitLab Basics =

== Introduction ==
Welcome to the first lab of Software Development Process and Testing (SDPT). In our lecture, we discussed why treating software like a physical breadboard leads to failure in complex systems. We introduced the Software Development Life Cycle (SDLC), Issue Tracking, and the underlying graph model of Git.

Today, we put theory into practice. By the end of this 2-hour lab, you will have:
# Created a project repository on GitLab.
# Created your first tracked Issue.
# Configured Git on your local machine.
# Moved a C++ source file through the Three States of Git.
# Pushed your local history to the remote GitLab server and automatically closed your Issue.

'''Note:''' Do not rush. The goal is to understand ''where'' your files are in the Git graph at any given moment. Run <code>git status</code> frequently!

---

== Part 1: Setting Up the Remote (GitLab) ==
Before we touch the terminal, we need to set up our remote infrastructure and document the work we intend to do.

=== 1. Create a New Repository ===
* Log into your university GitLab account.
* Click '''New Project''' -> '''Create blank project'''.
* '''Project Name:''' <code>sdpt-rfid-access</code>
* '''Visibility Level:''' Private (or Internal, depending on your professor's instructions).
* '''Important:''' Uncheck "Initialize repository with a README". We want an entirely empty repository to practice pushing from our local machine.
* Click '''Create project'''.

=== 2. Create Your First Issue ===
We need a business requirement before we write code.
* On the left sidebar of your new project, navigate to '''Plan''' -> '''Issues'''.
* Click '''New issue'''.
* '''Title:''' <code>Create initial RFID reader driver skeleton</code>
* '''Description:''' <code>Need a basic main.cpp file that will eventually hold the SPI communication logic for the RFID module.</code>
* Click '''Create issue'''.
* Take note of the '''Issue Number''' (e.g., <code>#1</code>) generated next to the title. You will need this later!

---

== Part 2: Initializing the Local Environment ==
Now, open your terminal (Linux/macOS) or Git Bash (Windows).

=== 1. Configure Your Identity ===
Git embeds the author's name and email into every commit permanently. You only need to run these commands once per computer.

<syntaxhighlight lang="bash">
git config --global user.name "Your First and Last Name"
git config --global user.email "your.university.email@domain.edu"
</syntaxhighlight>

=== 2. Create Your Local Workspace ===
Create a folder for your project and initialize it as a Git repository.

<syntaxhighlight lang="bash">
mkdir sdpt-rfid-access
cd sdpt-rfid-access
git init
</syntaxhighlight>

Notice the output: <code>Initialized empty Git repository</code>. A hidden <code>.git</code> folder has been created. This is your database.

---

== Part 3: The Three States in Practice ==
Remember the three states from the lecture: Working Directory, Staging Area, and Repository. Let's move a file through them.

=== 1. The Working Directory ===
Create a new C++ file. This represents writing your initial code.

<syntaxhighlight lang="bash">
touch main.cpp
</syntaxhighlight>

Open <code>main.cpp</code> in your favorite text editor (nano, vim, VS Code) and add a basic skeleton:

<syntaxhighlight lang="cpp">
#include <iostream>

int main() {
std::cout << "RFID Access Control System Initialized" << std::endl;
return 0;
}
</syntaxhighlight>

Now, check your radar:
<syntaxhighlight lang="bash">
git status
</syntaxhighlight>
''Notice that <code>main.cpp</code> is red and listed under "Untracked files". Git sees the file in your Working Directory, but is not managing it yet.''

=== 2. The Staging Area (Index) ===
Tell Git you want to include this file in your next commit snapshot.

<syntaxhighlight lang="bash">
git add main.cpp
git status
</syntaxhighlight>
''Notice the file is now green and under "Changes to be committed". It is in the Staging Area.''

=== 3. The Repository (Commit) ===
Save the snapshot permanently into your local Git database.

<syntaxhighlight lang="bash">
git commit -m "Add initial RFID system skeleton"
git status
</syntaxhighlight>
''Your working tree is now clean. The snapshot is stored as a node in your local Git graph.''

---

== Part 4: Connecting Local to Remote and Closing Issues ==
Your code is safe locally, but the "Bus Factor" is still 1. If your laptop crashes, the code is gone. We must push to GitLab.

=== 1. Link the Remote Server ===
Go back to your GitLab project page. Under "Push an existing Git repository", copy the <code>git remote add origin...</code> command. It will look like this:

<syntaxhighlight lang="bash">
git remote add origin https://gitlab.com/your-username/sdpt-rfid-access.git
</syntaxhighlight>

=== 2. Push and Close the Issue ===
We want to push our code AND tell GitLab that this code fulfills the requirement we documented in Part 1. We do this by making a new commit that references the Issue number.

Let's make a small change to <code>main.cpp</code>. Open it and add a comment:
<syntaxhighlight lang="cpp">
// TODO: Implement SPI communication with RC522 module
</syntaxhighlight>

Now, stage and commit this change, using a special keyword (<code>Closes #1</code>) in the commit message:

<syntaxhighlight lang="bash">
git add main.cpp
git commit -m "Add SPI TODO comment. Closes #1"
</syntaxhighlight>

Finally, push your local graph to the remote server:

<syntaxhighlight lang="bash">
git push -u origin main
</syntaxhighlight>
''(Note: If your default branch is 'master' instead of 'main', use <code>git push -u origin master</code>)''

=== 3. Verify the Magic ===
Go back to your browser and refresh your GitLab project page:
* Your <code>main.cpp</code> file is now visible on the server!
* Go to '''Plan''' -> '''Issues'''. Notice that Issue #1 is now automatically marked as '''Closed'''. Git and GitLab worked together to link your code directly to the business requirement.

---

== Lab Deliverable ==
To receive full credit for this week's lab, call the professor or teaching assistant over to your workstation and demonstrate:
# Your GitLab repository showing the <code>main.cpp</code> file.
# Your GitLab Issue board showing Issue #1 as Closed.
# Your terminal showing the output of the <code>git log</code> command, displaying your two commits.

@@ Linia 20: / Linia 20: @@
 Open your terminal (Linux/macOS) or Git Bash (Windows) and type:
 <syntaxhighlight lang="bash">
-ssh-keygen -t ed25519 -C "your.university.email@domain.edu"
+ssh-keygen -t ed25519 -C "your.university.email@stud.####.upb.ro"
 </syntaxhighlight>
 * Press '''Enter''' to accept the default file location.

@@ Linia 141: / Linia 141: @@
 git status
 </syntaxhighlight>
 == Part 6: Connecting Local to Remote and Closing Issues ==
@@ Linia 179: / Linia 177: @@
 * Your <code>main.cpp</code> and <code>.gitignore</code> files are visible!
 * Go to '''Plan''' -> '''Issues'''. Notice that Issue #1 is now automatically marked as '''Closed'''.
 == Lab Deliverable ==

SDPT Lab 1 - Revizia istoricului

Rhobincu: /* Part 1: Secure Authentication (SSH Keys) */

Rhobincu la 23 februarie 2026 00:40

Rhobincu la 23 februarie 2026 00:39

Rhobincu: Pagină nouă: = Lab 1: Foundation of Process - Git and GitLab Basics = == Introduction == Welcome to the first lab of Software Development Process and Testing (SDPT). In our lecture, we discuss...