docs.shellr.net

Projects

Projects aligned with the current portfolio and resume track.

The project set around shellr combines live platform operations, application work, reporting automation, migration and hardening, self-hosted websites, and current security-focused automation work. The goal is to show a realistic path from practical systems work to structured platform ownership.

Last reviewed: September 2026 Scope: current and historical Review angle: problem, boundary, outcome
How to read this page Not every project is a full standalone product. Some are live surfaces, some are operational building blocks, and one is active security automation work. Together they show the progression from self-hosted systems work toward platform, monitoring, and automation responsibilities.

Genesis / self-hosted platform

Status: current

Single-VM platform on Hetzner with Docker Compose, Nginx, TLS, monitoring, logging, backup, and documented recovery.

  • Public entrypoints routed through Nginx with clear hostname boundaries.
  • Compose-managed separation for app, DMA, monitoring, logging, and stateful services.
  • Operational continuation of earlier migration and hardening work.

DMA statistics module

Status: read-only public showcase

Read-only architecture showcase for an API-based match-statistics workload originally implemented as its own PHP runtime on dma.shellr.net.

  • Aggregates JSON data from external sources into player and champion views.
  • Runs with separate routing, health behavior, and database scope.
  • Public access is limited to project context; interactive and write paths are not exposed.

Automated web analytics with AWStats

Status: documented reference workflow

Reference reporting path for access and usage data derived from webserver logs.

  • Includes a sanitised AWStats configuration and cron-ready generator.
  • Requires an explicit access-log path before being enabled in production.
  • Fits the resource model of a single host and a small operational setup.

Web platform migration and hardening

Status: completed / ongoing practice

Migration of web workloads onto Linux-based infrastructure with stronger security and clearer operations.

  • Includes host hardening, access control, and stable service reachability.
  • Focuses on controlled change steps instead of risky rewrites.
  • Directly informs the structure of the current public platform.

Inventory tracking application

Status: application workload

Web-based inventory software used as a practical CRUD workload for the platform.

  • Built with PHP, JavaScript, and a relational database.
  • Manages and presents stock data in a structured UI.
  • Provides a simple but realistic app layer for deployment and backup decisions.

Vulnerability relevance automation

Status: current security automation work

Automation work focused on turning vulnerability feeds into asset-relevant review tasks.

  • Uses the ENISA EUVD API as an upstream data source.
  • Maps vulnerability data against an asset inventory and adds CVSS, KEV, and EPSS context.
  • Targets repeatable triage and notification instead of manual feed review.