🌍 Looking for a Serious Collaboration Partner 🤝 I am looking for a sincere and reliable partner to explore new business and online collaboration opportunities together. Whether you have fresh ideas, need a development team to bring your project to life, or are looking for a co-founder to help grow something successfully, I would be happy to connect. My goal is to work with someone who is honest, responsible, and truly interested in building profit together through long-term cooperation. If you are interested, please send me a DM. Let’s discuss how we can collaborate and grow together.

Challenge 3: Document Your Home Lab in Git Repository: https://github.com/brandonleegit/homelabexplorers.git Folder: challenges/<your-github-username>-challenge3/ ⚠️ IMPORTANT: Do not commit any sensitive information—redact or anonymize IP addresses, hostnames, credentials, keys, or any other secrets before you push your changes. What to Do - Clone the Repo - git clone https://github.com/brandonleegit/homelabexplorers.git - cd homelabexplorers Create a New Branch - git checkout -b docs/home-lab-inventory - Create Your Challenge Folder under the root /challenges folder - mkdir -p challenges/$(git config user.username)-challenge3 - cd challenges/$(git config user.username)-challenge3 - Add Your Documentation Hardware Inventory (hardware.md) - List each device (e.g., “Server-1: Dell R420, 2×E5-2650, 64 GB, 4 × 4 TB”, IP: 10.1.X.X – redact last octet). Network Topology (network.md) - Describe VLANs, subnets, uplinks. Redact exact IPs (e.g., 192.168.1.X). Optionally include an ASCII or PlantUML diagram. Services & Workloads (services.md) - Catalog VMs, containers, clusters, key apps (e.g., “Prometheus on VM-2, Gitea on container-1”). - Configuration Snippets (configs/) Add sanitized versions of critical .yml or .conf files (e.g., remove API keys, passwords). Stage & Commit - git add challenges/$(git config user.username)-challenge3 - git commit -m "docs: add home-lab documentation for Challenge 3" Push & Open a PR - git push origin docs/home-lab-inventory - Then open a pull request against main. Share Your Submission - Post the PR link (or the commit SHA) back in the “Challenges” thread. - Call out one tricky part you documented (e.g., your VLAN tagging approach or a custom storage config).

Everyone @David Vincent had a great idea to create a repo for all the challenge docs, files, configs, code, etc. I have created an official "HomeLabExplorers" repo here: https://github.com/brandonleegit/homelabexplorers.git As David mentioned, this will also serve the purpose of ones getting familiar with Git as well, with their home lab projects. I have created the repo that contains a "challenges" folder. So you will just need to clone it down and create pull requests to have your code merged in. I think possibly a good idea would be to use your HomeLabExplorers name or any name for your subfolder underneath and maybe create folders for "challenge 1" challenge 2, etc. However, let me know your thoughts as this is a work in progress. Thanks Everyone!

Learn how to create your first pull request (PR)! What's the last command to complete this challenge? To complete this task 100%. The first command executed was: git config --global user.name "bleevhttest" I couldn't see the second one in the video. Could you help?

🚀 Home Lab Challenge #2: Monitor It, Automate It, Scale It! In the last challenge, you laid the foundation — whether that was your first Proxmox VM, your first Docker container, or even deploying Nginx Proxy Manager for routing apps. This week, we’re kicking things up a notch with new challenges focused on observability, automation, and scaling your home lab stack. This round of challenges is designed to take your setup from "it works" to "I can see it, automate it, and scale it." Pick your tier, declare it in the thread, and share your progress all week long. And remember, this is a group mission. Ask questions. Post screenshots. Drop tips. Let’s level up together. 🟢 Level 1 – Beginner: “Know What’s Happening” Challenge: Set up container-level monitoring - Install cAdvisor and Node Exporter in Docker - Use Prometheus + Grafana or just a basic Prometheus dashboard to monitor CPU, memory, and container usage - Bonus: Add an alert rule to notify if a container crashes or hits a memory limit Goal: Start seeing inside your containers and get comfortable reading resource metrics. 🟡 Level 2 – Intermediate: “Automate the Boring Stuff” Challenge: Automate app deployment with Docker Compose or Ansible - Convert one of your existing manually-installed apps to a docker-compose.yml stack - Or, write a basic Ansible playbook that installs Docker and deploys an app on a remote host - Bonus: Set up automatic updates using Watchtower or Shepherd Goal: Get repeatable deployments and start thinking like a DevOps pro. 🔵 Level 3 – Advanced: “Make It Resilient & Scalable” Challenge: Add high availability or resilience to your apps - Use Docker Swarm to deploy an app across multiple nodes - Or use Kubernetes to create a deployment with multiple replicas and a LoadBalancer or Ingress - Bonus: Test what happens if one node goes down — do your apps stay up? Goal: Learn the building blocks of HA setups and resilience strategies.