X_Δ
Developer, homelab builder, event-tech operator, and systems tinkerer focused on practical infrastructure, automation, networking, and real-world technical problem solving.
Bio
I study electrotechnics and automotive IT at BMSZC Bolyai János Technical School. My work sits between software, infrastructure, electronics, live production, and networking.
I also work with event technology, including lighting, audio, visual effects, special effects, and electrical systems for concerts and live events.
On the software side, I build tools, dashboards, bots, automation scripts, monitoring systems, and self-hosted services using Linux, Windows, Proxmox, Docker, Nginx, PHP, Node.js, Python, and Bash.
I am also working toward HAREC certification to expand further into RF communication, amateur radio, and emergency communications.
Overview
I like building systems that connect the digital and physical world: servers, scripts, dashboards, lighting control, field networks, monitoring, and automation. My focus is not one specific stack; it is building reliable workflows that solve real problems.
Current direction: combining homelab automation, event infrastructure, and field-ready networking into portable, resilient technical setups.
Technical Focus
Infrastructure
- Proxmox virtualization
- Docker and containerized services
- Nginx reverse proxies and web hosting
- Monitoring, alerting, and backups
Development
- Full-stack web tools and dashboards
- Backend APIs and automation controllers
- Batch, Bash, Python, PHP, JavaScript, C/C++
- Practical scripts that evolve into frameworks
Networking
- Routing, DHCP, DNS, VLANs, VPNs
- Portable networks for events and field setups
- Wireless access, interference mitigation, and uptime planning
- Server-to-server links and redundant access paths
Event Technology
- Lighting rigs and DMX-style workflows
- Audio systems and live technical operation
- Power distribution and electrical safety
- Show networks and temporary infrastructure
Systems I Use
- Linux for servers, development, automation, and infrastructure work.
- Windows for compatibility, testing, tools, and certain production workflows.
- VS Code for scripting, web development, and multi-language projects.
- Visual Studio for larger C/C++ and .NET workflows.
- Terminal-first workflow using Bash, PowerShell, and shell automation.
Languages & Tools
Low-Level / Desktop
- C
- C++
- Java
- .NET / C# basics
Web
- HTML / CSS / JavaScript
- Node.js
- PHP
- Nginx deployments
Scripting / Automation
- Python
- Bash
- Batch
- PowerShell
- Lua
PowerEdge R630 Compute Cluster
- Multiple Dell PowerEdge R630 nodes
- Dual 14-core CPUs per node
- Up to 56 threads per node
- ECC memory and mixed SSD/HDD storage
- Hypervisor: Proxmox VE
- Workloads: web services, Minecraft infrastructure, backend/frontend systems, testing environments
- Networking: routed access, tunnels, gateway integration, and backup paths
IBM Storage Nodes
- ECC-based storage systems
- TrueNAS CORE with IPMI management
- RAID boot storage
- Multi-drive HDD pools with cache storage
- Role: file storage, compression, backups, and internal data management
Portable HomeLab
A compact field-ready setup designed for temporary networks, events, remote access, and mobile infrastructure.
- Huawei 4G CPE used as the primary mobile uplink.
- TP-Link ER706W Omada gateway for routing, firewall, VPN, and DHCP.
- Custom UPS-backed power setup for portable operation and low downtime.
- Two Raspberry Pi 3B+ nodes for lightweight compute and independent services.
- Samsung M.2 SSD storage for portable data and service hosting.
- Cudy outdoor PoE access point for wireless coverage.
Event Experience
I have worked on live events, concerts, and parties where the technical side mattered as much as the program itself: power distribution, lighting, audio, network reliability, cabling, and operational safety.
My largest hosted setup so far was a 9th-grade welcome party with over 170 attendees. The build involved a full concert-style technical deployment: digital mixers, moving heads, rod lights, strobes, subwoofer arrays, top speakers, microphones, patching, long cable runs, and a dedicated event network.
My role focused heavily on networking and reliability: custom RouterBox deployment, interference mitigation, anti-jamming considerations, and communications planning to keep the production network stable during the event.
Note: power and electrical work should always be planned and checked according to local regulations, site limits, and proper safety procedures.
Networking & Integration
- Low-latency links between compute and storage nodes.
- Routed access between services, gateways, and backup paths.
- DNS, DHCP, firewall, VPN, and reverse-proxy integration.
- Experience with LAN-party and Minecraft server infrastructure under heavy load.
- Portable network design for events and temporary deployments.
SpaceCraftMC Infrastructure
- Velocity proxy with region-based routing and forced-host logic.
- Multi-node server layout running on Dell R630 infrastructure.
- Automated restarts, monitoring, and patched plugin stacks.
- Designed for scalability, service separation, and controlled backend routing.
KRÉTA / xDev School Tools
- Schedule and countdown tools with a secure backend controller.
- JSON-based caching and fast frontend updates.
- Modular PHP structure for easy extension and maintenance.
- Designed for school dashboards, kiosk displays, and internal tools.
Projects
OMEGA / BatchRack
OMEGA is an experimental Batch-based command environment focused on control, persistence, plugin loading, encryption experiments, and Windows automation.
- OMEGA I: early command shell and parser foundation.
- OMEGA II: plugin loading, basic security layers, and filesystem simulation.
- OMEGA III: encryption experiments and isolation concepts.
- BatchRack / OMEGA IV: integrated kernel-style runtime with plugins and sandbox persistence.
Purpose: pushing Windows Batch beyond normal scripting use and exploring how far a constrained environment can be extended.
RPlotSquared Builds
Private patched build workflow using Gradle. This is build and integration work, not original ownership of the upstream source.
Automation
I automate repetitive infrastructure work wherever it makes sense: systemd services, Bash scripts, Python utilities, scheduled backups, dynamic DNS updates, monitoring hooks, and Discord-based alerts.
The goal is simple: fewer manual steps, faster recovery, cleaner visibility, and less time wasted repeating the same fix twice.