[{"content":"WIP might drift to talos OS Building my own homelab as I have a spare PC, it\u0026rsquo;s been 6 years my pc have an upgrade and instead selling my old pc, I try to build homelab there are things are very repititive and let\u0026rsquo;s try to eliminate that. seem\u0026rsquo;s this homelab will try to fix those things. also this will open and learn other things.\nHardware PC sepcs: Cpu: Ryzen 7 3700x Gpu: Quadro P400 PSU: 550 watts Cpu Coolermaster Ram: 8 + 4 = 12gb RAM total memory Mobo: Gigabyte 520I AC SSD: SkHynix 256Gb HDD: 1tb drive Will most of it are my old pc parts, some of the parts I already sold, also I left at home. I just buy a Gpu just to intiate Boot and Quardo p400 have a dedicated hardware video encoding engine, commonly known as NVENC. This will support NAS media. A Ryzen 7 3700x will be good handling multithreading task.\nFor this setup I use Fedora server distro, Installing is easy yo follow. Link to download download the For Intel and AMD x86_64 systems cause I\u0026rsquo;m using the Ryzen 7 3700x.\nReference: https://docs.fedoraproject.org/en-US/fedora-server/\nTools to install When installing just use the dnf package manager.\nbtop - Good overview of hardware observability snapshot of my machine. which is a c lang tui. nvim - a minimal vim config only to get started with the files should I edit. tmux - A good terminal flexibility tool that allows you to manage multiple terminal sessions within a single window. git - to install necessary tools to get started and manage code. Initial SSH Setup The Goal is to have a Remote administration via SSH, Passwordless authentication and Key-based authentication only for secure access.\nGenerate SSH Key (if needed) ssh-keygen -t ed25519 -C \u0026#34;homelab\u0026#34; Copy Public Key to Fedora Server machine we will use this prefered method. Preferred method:\nssh-copy-id user@server-ip Manual fallback:\ncat ~/.ssh/id_ed25519.pub On Fedora Server:\nmkdir -p ~/.ssh chmod 700 ~/.ssh nvim ~/.ssh/authorized_keys chmod 600 ~/.ssh/authorized_keys Paste public key contents into:\n~/.ssh/authorized_keys Test Passwordless SSH\nFrom your access machine\nssh user@server-ip 2. Disable Password Authentication\nEdit SSH Configuration sudo nvim /etc/ssh/sshd_config Recommended settings:\nPasswordAuthentication no ChallengeResponseAuthentication no PubkeyAuthentication yes PermitRootLogin no Restart ssh\nsudo systemctl restart sshd Firewall Configuration Enable firewalld\nsudo systemctl enable --now firewalld Allow SSH Access\nsudo firewall-cmd --add-service=ssh --permanent sudo firewall-cmd --reload Verify Firewall Rules sudo firewall-cmd --list-all Static IP Configuration, Identify Network Interface nmcli device status\nExample:\neth0 ethernet connected Check Connection Name nmcli connection show Example:\nWired connection 1 Configure Static IP Example configuration:\nsudo nmcli connection modify \u0026#34;Wired connection 1\u0026#34; \\ ipv4.addresses 192.168.1.50/24 \\ ipv4.gateway 192.168.1.1 \\ ipv4.dns \u0026#34;1.1.1.1 8.8.8.8\u0026#34; \\ ipv4.method manual Apply configuration:\nsudo nmcli connection down \u0026#34;Wired connection 1\u0026#34; sudo nmcli connection up \u0026#34;Wired connection 1\u0026#34; Verify IP Address\nip a Hostname Configuration Set Hostname\nsudo hostnamectl set-hostname fedora-homelab Verify Hostname\n","permalink":"https://louieladiona.pages.dev/knowledge-base/lab-setup/","summary":"\u003ch1 id=\"wip-might-drift-to-talos-os\"\u003eWIP might drift to talos OS\u003c/h1\u003e\n\u003cp\u003eBuilding my own homelab as I have a spare PC, it\u0026rsquo;s been 6 years my pc have an upgrade and instead selling my old pc, I try to build homelab there are things are very repititive and let\u0026rsquo;s try to eliminate that. seem\u0026rsquo;s this homelab will try to fix those things. also this will open and learn other things.\u003c/p\u003e\n\u003ch2 id=\"hardware\"\u003eHardware\u003c/h2\u003e\n\u003cp\u003e\u003cimg alt=\"PC\" loading=\"lazy\" src=\"/images/homelab/open_pc.jpg\"\u003e\u003c/p\u003e\n\u003ch3 id=\"pc-sepcs\"\u003ePC sepcs:\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003eCpu: Ryzen 7 3700x\u003c/li\u003e\n\u003cli\u003eGpu: Quadro P400\u003c/li\u003e\n\u003cli\u003ePSU: 550 watts Cpu Coolermaster\u003c/li\u003e\n\u003cli\u003eRam: 8 + 4 = 12gb RAM total memory\u003c/li\u003e\n\u003cli\u003eMobo: Gigabyte 520I AC\u003c/li\u003e\n\u003cli\u003eSSD: SkHynix 256Gb\u003c/li\u003e\n\u003cli\u003eHDD: 1tb drive\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWill most of it are my old pc parts, some of the parts I already sold, also I left at home. I just buy a Gpu just to intiate Boot and Quardo p400 have a dedicated hardware video encoding engine, commonly known as NVENC. This will support NAS media. A Ryzen 7 3700x will be good handling multithreading task.\u003c/p\u003e","title":"My Home Lab Setup"},{"content":"Creating my personal site (the one you’re reading right now). I used a static site generator called Hugo. I picked it mainly because I’m already a bit familiar with Go, but the nice thing is you don’t actually need to know Go at all to use it. It’s simple, fast, and gets out of your way. In this post, I just want to walk through how I got started and how I began building my own documentation space.\nGetting Started with Hugo First things first: installation. Hugo has solid documentation that covers different environments, so it’s best to follow their official installation guide depending on your setup.\nOnce installed, I’d strongly recommend going through their “Getting Started” section. It gives you a clear idea of how everything fits together.\nTo create a new site, just run:\nhugo new site \u0026lt;name\u0026gt; Hugo immediately gives you helpful next steps, which is a nice touch. After that:\ncd \u0026lt;name\u0026gt; Choosing a Theme This part honestly took me the longest. There are hundreds of themes available, and picking one isn’t exactly straightforward. I wish there were better filters, but I eventually realized they’re roughly sorted by GitHub stars.\nThat led me to the PaperMod theme. It checked all the boxes for me: clean, minimal, blog-friendly, and with dark mode support. The documentation also looked solid, which made the decision easier.\nIf you want to in dept features of PaperMod\nTo set it up, I initialized a Git repository:\ngit init Then added the theme as a submodule:\ngit submodule add --depth=1 https://github.com/adityatelange/hugo-PaperMod.git themes/PaperMod Configuring the Site Hugo uses a configuration file, typically hugo.toml. I switched mine to YAML since I’m more comfortable with it.\nHere’s a simple starting point:\nbaseURL: \u0026#34;\u0026#34; languageCode: en-us title: Your Name theme: PaperMod Once that’s in place, you can spin up your site locally:\nhugo server -D The -D flag includes draft content, and Hugo’s live reload makes development really smooth. Just keep the server running while you work.\nCreating Content Adding content is straightforward:\nhugo new content posts/my-first-post.md This creates a Markdown file inside the content folder. Hugo also generates some default metadata at the top:\n+++ title = \u0026#39;My First Post\u0026#39; date = 2023-11-12T22:40:04+02:00 draft = true +++ You can edit the title and start writing your content right below it. Save the file, and you’ll instantly see it reflected on your local site.\nIf you prefer YAML over TOML (like I do), you can tweak the archetype template in the archetypes folder.\nAdding a Menu To add a simple navigation menu, update your config file:\nmenu: main: - identifier: posts name: Posts url: /posts/ weight: 10 - identifier: tags name: Tags url: /tags/ weight: 20 - identifier: search name: Search url: /search/ weight: 30 You can also tag your posts by adding something like:\ntags: [\u0026#39;tag1\u0026#39;, \u0026#39;tag2\u0026#39;] Then just navigate to the tags page to see them in action.\nOne small quirk I noticed: sometimes the site doesn’t reload properly. Saving the config file usually fixes it.\nAdding Search The search page doesn’t exist by default, so you’ll need to create it:\nhugo new content search.md Then update its metadata:\n--- title: \u0026#34;Search\u0026#34; layout: \u0026#34;search\u0026#34; summary: \u0026#34;search\u0026#34; placeholder: \u0026#34;start typing here ...\u0026#34; --- Customizing the Homepage To add a bit of personality to the homepage, you can include an intro and social links:\nparams: homeInfoParams: title: Some fancy text... Content: This is my personal blog... socialIcons: - name: github url: \u0026#34;https://github.com/username\u0026#34; - name: linkedin url: \u0026#34;https://linkedin.com/in/username\u0026#34; Just swap in your own links and text.\nFinal Thoughts At this point, things already start to look pretty good.\nWhat I really like about Hugo is how everything is file-based and content is just Markdown. It keeps things simple and flexible. And if you ever want to tweak something, you can dive into the HTML, CSS, or JavaScript and make it your own.\nIf you want to go deeper, the documentation is extensive and well-written. There’s a lot you can do once you get comfortable with the basics.\n","permalink":"https://louieladiona.pages.dev/posts/hugo-site/","summary":"\u003cp\u003eCreating my personal site (the one you’re reading right now). I used a static site generator called Hugo. I picked it mainly because I’m already a bit familiar with Go, but the nice thing is you don’t actually need to know Go at all to use it. It’s simple, fast, and gets out of your way. In this post, I just want to walk through how I got started and how I began building my own documentation space.\u003c/p\u003e","title":"Personal Page with Hugo"}]