🖥️ FLV homelab

A personal cloud homelab offers several advantages, making it an appealing choice for tech enthusiasts and privacy-conscious users. First, it provides full control over your data, ensuring privacy and security without relying on third-party services. You can customize the setup to suit your needs, whether it's for file storage, media streaming, or hosting applications. It also allows for offline access and backup, ensuring you are never dependent on an external service's uptime. Additionally, managing your own cloud fosters learning in areas like networking, server management, and automation, which can be both educational and empowering. Tecnology indipendence need to be implemented starting from my home.

• 2007 Toshiba tecra laptop (first headless machine=broken LCD) 512Mb ram
• 2013 good old IBM thinkpad Intel centrino 2 cores, 1Gb ram, good memory of blue <ENTER> key. First homelab server
• 2016 second homelab server Pine64 2Gb ram ARM era has started
• 2019 third homelab server RaspberryPI IV 8Gb ram storage with 500Gb 3.5" Barracuda
• 2021 water discovered: hobbyist single board is not suitable for server workload
• 2022 Welcome Zimaboard + Proxmox

This document provides a comprehensive breakdown of the homelab network, including hosts, tasks, and documentation.

A simple org-mode document with a simple custom CSS is my personal tool for homelab resource mapping.

Proxmox primary node, host several LXC container and Virtual Machines, provide large storage via lvm.

• Proxmox Virtual Environment
• Nut UPS monitor

fanless mini appliance dedicated to Proxmox backup service may run other small services

• backup storage bay mypbs hosts all zimaserver scheduled backups
• NFS export for other than Proxmox backups

This machine replicate flvbox.org OpenBSD 7.6 environment. Every release cycle is tested here before flvbox.org sysupgrade.

• OpenHTTPD with relayd and uwsgid

My personal multi-service LXC container, some Django|Flask|Streamlit|Node personal apps

• Django main project in /var/www/piserver-production managed by apache, this is the main portal
• Self signed certificate for https
• Postfix smtp only local
• Code-server: listen on port 8080
• Webcam: port 8001 via dedicated Flask app in /var/www/dj_video
• RedisCommander: port 8081
• NFS server exports under /srv/nfs4/
• zimaserver UPS control via /home/flavio/ups-monitor/ups-monitor.py
• FlvCry: Flask webapp for crypto-ops, port 8088 unit: flvcry.service
• FlvCloud: streamlit portal, port 8501 unit: flvcloud.service, this is the secondary portal
• JupyterLab: port 8888 unit: jupyter-lab.service
• FlvGeoLoc: Flask webapp for geolocate me, port 5000 unit: flvgeoloc.service
• MySQL MariaDB Distrib 10.5.26-MariaDB

DHCP server with PXE boot environment provided by dnsmasqd, serve all 192.168.5.0/24 subnet via ZyXEL GS1100-16 ethernet switch.

Important services reiceve per host DHCP configuration (static IP, PXE boot server/options)

• DHCP and PXE boot environment via dnsmasqd
• HTTP via Nginx http://dhcp.my.zimaserver/tftp/ tftp resources dir with autoindex
• FLV rustic ADblocker populate dinamically /etc/alternate_hosts that's redirect all scams to 0.0.0.0
• DNS name resolution service take in account /etc/alternate_hosts

Private, Fast, Reliable DevOps Platform. Brings teams and developers high-efficiency but easy operations from planning to production.

• Gitea at https://gitea.my.zimaserver/
• my repositories hosts all homelab services

Uptime Kuma is an easy-to-use self-hosted monitoring tool.

• Uptime Kuma monitoring dashboard at http://uptimekuma.my.zimaserver:3001

Redis (Remote Dictionary Server) is a source-available, in-memory storage, used as a distributed, in-memory key–value database, cache and message broker, with optional durability.

• Redis listen on internal and vpn
  • [X] migrated to Valkey

Get Google search results, but without any ads, JavaScript, AMP links, cookies, or IP address tracking.

• Whoogle Search listen on internal and vpn, port 5000

Trilium Notes is a hierarchical note taking application with focus on building large personal knowledge bases.

• Trilium listen on internal , port 8080, http://trilium.my.zimaserver:8080

Personal blog

• BE: Django application that provides a RESTful API for managing blog posts. The API allows clients to list, create, retrieve, update, and delete posts. The application is built using Django and Django Rest Framework (DRF).
• FE: React front-end, custom CSS in order to avoid bootstrap or similar frameworks.

• Django backend listen on internal , port 8000, http://blog.my.zimaserver:8000
• React frontend listen on internal and vpn, port 80, http://blog.my.zimaserver

lf aka father personal cloud space, data vault, app server.

• VPN gateway from internal network set default route to lfserver allow traffic with OpenVPN vpn (layer 2)
• OpenSSH listen on internal and vpn
• BibliotecaCasalinga tiny Django app, port 8000, listen on internal and vpn