hasan.
Completed

Runtime Garden Development Infrastructure

My personal VPS environment for running Docker containers, managing applications and automating server maintenance.

  • Ubuntu 24.04 LTS
  • Docker
  • Docker Compose
  • Dockge
  • NGINX Proxy Manager
  • systemd
  • Cloudflare
Runtime_Garden_Dev_Server_Architecture_Project

Runtime Garden is my personal server infrastructure project. It brings together Docker-based application hosting, reverse proxy management and automated maintenance on a single VPS. I designed the setup around Ubuntu 24.04 LTS, Docker Compose, Dockge and NGINX Proxy Manager. The architecture also includes plans for running different types of applications and connecting them to external AI providers. Alongside the infrastructure, I documented the server architecture, management access and Docker cleanup process. I also separated verified components from planned features so the documentation reflects what is known about the current setup. The project is an ongoing effort to build a practical and organized environment for hosting my own applications and experiments.

Problem

I wanted a simple way to host and manage my own applications on a VPS. I needed a place to manage Docker Compose stacks, route web traffic and handle routine maintenance. I also wanted to keep administrative access separate from public application traffic. As the number of services grows, it becomes harder to keep track of deployments, storage and access rules. I wanted to document the setup clearly and separate verified components from planned features.

Approach

Runtime Garden uses Ubuntu 24.04 LTS as its base operating system with Docker Engine and Docker Compose for container management. The architecture includes Dockge for managing Compose stacks and NGINX Proxy Manager for routing HTTP and HTTPS traffic. SSH tunnels are the preferred way to access administration interfaces. Cloudflare is an optional part of the design. I also configured a systemd timer to run Docker image and build cache cleanup every Sunday at 04:00 UTC. The cleanup uses a seven-day filter. I documented the observed Docker state and marked components that still need verification.Runtime_Garden_Dev_Server_Architecture

Results

The server snapshot confirmed that Docker was running four containers and had five images and one local volume. The build cache contained 18 entries with about 773 MB reported as reclaimable. I manually ran the cleanup service on 11 October 2026. It completed successfully but reclaimed 0 bytes because the seven-day filter did not match the available build cache. The architecture documentation now separates observed server state from the planned design. Network access, persistent storage mappings and some application components still need verification.

Gallery

Runtime_Garden_Dev_Server_Architecture