Merge branch 'inno-devops-labs:master' into master

Author: Brvcket

lab3.md

@@ -0,0 +1,83 @@
+# Version Control
+
+In this lab, you will learn about version control systems and their importance in collaborative software development. You will specifically focus on Git, one of the most widely used version control systems. Follow the tasks below to complete the lab assignment.
+
+## Task 1: Understanding Version Control Systems
+
+**Objective**: Understand how Git stores data.
+
+1. **Create and Explore a Repository**:
+   - Use the current repository and make a few commits.
+   - Use `git cat-file` to inspect the contents of blobs, trees, and commits.
+
+     ```sh
+     # Example commands to inspect contents
+     git cat-file -p <blob_hash>
+     git cat-file -p <tree_hash>
+     git cat-file -p <commit_hash>
+     ```
+
+   - Create a `submission3.md` file.
+   - Provide the output in the `submission3.md` file.
+
+## Task 2: Practice with Git Reset Command
+
+**Objective**: Practice using different ways to use the `git reset` command.
+
+1. **Create a New Branch**:
+   - Create a new branch named "git-reset-practice" in your Git repository.
+
+     ```sh
+     git checkout -b git-reset-practice
+     ```
+
+2. **Explore Advanced Reset and Reflog Usage**:
+   - Create a series of commits.
+
+     ```sh
+     echo "First commit" > file.txt
+     git add file.txt
+     git commit -m "First commit"
+     
+     echo "Second commit" >> file.txt
+     git add file.txt
+     git commit -m "Second commit"
+     
+     echo "Third commit" >> file.txt
+     git add file.txt
+     git commit -m "Third commit"
+     ```
+
+   - Use `git reset --hard` and `git reset --soft` to navigate the commit history.
+
+     ```sh
+     git reset --soft HEAD~1
+     git reset --hard HEAD~1
+     ```
+
+   - Use `git reflog` to recover commits after a reset.
+
+     ```sh
+     git reflog
+     git reset --hard <reflog_hash>
+     ```
+
+3. **Documentation**:
+   - Document the steps taken and push the final state to GitHub.
+   - Document your practice in the `submission3.md` file and include the following details:
+     - Steps you took to perform the Git reset operations.
+     - Explain the reset and reflog process in the `submission3.md`.
+     - Examples and outputs of the commands executed.
+
+## Additional Resources
+
+- [Git Documentation](https://git-scm.com/doc)
+- [Pro Git Book](https://git-scm.com/book/en/v2)
+
+### Guidelines
+
+- Use proper Markdown formatting for documentation files.
+- Organize files with appropriate naming conventions.
+- Create a Pull Request to the main branch of the repository with your completed lab assignment.
+
+> Note: Actively explore and document your findings to gain hands-on experience with Git.

lab4.md

@@ -0,0 +1,119 @@
+# Software Distribution
+
+In this lab, you will explore software distribution strategies and best practices. You will gain insights into the different approaches used to distribute software and understand the importance of effective software distribution in the development lifecycle. Follow the tasks below to complete the lab assignment.
+
+## Task 1: Configure and Use a Local Package Repository
+
+**Objective**: Set up a local package repository and use it to install packages.
+
+1. **Create a Local Repository**:
+   - Create a directory to hold your repository and place some `.deb` files in it.
+
+     ```sh
+     mkdir -p ~/local-apt-repo
+     cp /path/to/package.deb ~/local-apt-repo/
+     ```
+
+2. **Generate the Package Index**:
+   - Use `dpkg-scanpackages` to create a `Packages` file. Compress this file into a `Packages.gz` archive.
+
+     ```sh
+     dpkg-scanpackages ~/local-apt-repo /dev/null | gzip -9c > ~/local-apt-repo/Packages.gz
+     ```
+
+3. **Add the Local Repository to Your Sources List**:
+   - Add the repository to your `sources.list`.
+
+     ```sh
+     echo "deb [trusted=yes] file:/home/yourusername/local-apt-repo ./" | sudo tee /etc/apt/sources.list.d/local-apt-repo.list
+     sudo apt update
+     ```
+
+4. **Verify the Contents of the Packages.gz File:**:
+   - Check that the Packages.gz file contains the correct paths and metadata for your .deb files, **it must be relative path like `./your_package.deb`**. Also you can see the package name there. Then check the repository of your package, make sure it's local one.
+
+     ```sh
+     zcat Packages.gz
+     apt policy your-package-name
+     ```
+
+5. **Install a Package from the Local Repository**:
+   - Install a package using `apt` from your local repository.
+
+     ```sh
+     sudo apt install your-package-name
+     ```
+
+6. **Document the Process**:
+   - Create a `submission4.md` file.
+   - Provide step-by-step documentation of your setup and installation process in the `submission4.md` file.
+
+## Task 2: Simulate Package Installation and Identify Dependencies
+
+**Objective**: Use `apt` to simulate package installation and identify dependencies without actually installing the packages.
+
+1. **Choose a Package to Simulate**:
+   - Select a package to simulate its installation.
+
+     ```sh
+     apt-cache showpkg your-package-name
+     ```
+
+2. **Simulate the Installation**:
+   - Use the `-s` flag to simulate the installation.
+
+     ```sh
+     sudo apt-get install -s your-package-name
+     ```
+
+3. **Analyze the Output**:
+   - Identify the dependencies and the packages that would be installed.
+   - Document the findings in the `submission4.md` file, including which dependencies are required and their versions.
+
+## Task 3: Hold and Unhold Package Versions
+
+**Objective**: Prevent a package from being upgraded and then allow it to be upgraded again.
+
+1. **Install a Package**:
+   - Install a package that is commonly updated.
+
+     ```sh
+     sudo apt install your-package-name
+     ```
+
+2. **Hold the Package**:
+   - Use `apt-mark` to hold the package.
+
+     ```sh
+     sudo apt-mark hold your-package-name
+     ```
+
+3. **Verify the Hold Status**:
+   - Check the status of held packages.
+
+     ```sh
+     apt-mark showhold
+     ```
+
+4. **Unhold the Package**:
+   - Use `apt-mark` to unhold the package.
+
+     ```sh
+     sudo apt-mark unhold your-package-name
+     ```
+
+5. **Documentation**:
+   - Document the steps taken to hold and unhold the package, including any verification commands in the `submission4.md` file.
+
+## Additional Resources
+
+- [Apt Documentation](https://manpages.debian.org/buster/apt/apt.8.en.html)
+- [Debian Package Management](https://www.debian.org/doc/manuals/debian-faq/pkg-basics.en.html)
+
+### Guidelines
+
+- Use proper Markdown formatting for documentation files.
+- Organize files with appropriate naming conventions.
+- Create a Pull Request to the main branch of the repository with your completed lab assignment.
+
+> Note: Actively explore and document your findings to gain hands-on experience with `apt` and software distribution strategies.