The documented Azure lab brings together hosting, containers, APIs, and data. This diagram explains the intended design; it does not assert that each service is currently running.

01 / ACCESS

Visitor

Browser · HTTPS

→

02 / ROUTING

Caddy

Reverse proxy · TLS

→

03 / APPLICATION

Docker services

Portfolio · Flask API

→

04 / DATA

PostgreSQL

Application persistence

Azure Ubuntu VM
Documented lab environment

GitHub → validation → release
Version-controlled website delivery

WireGuard
Separate private networking environment

OBSERVABILITY, WITHOUT GUESSWORK

Monitoring unavailable

No verified infrastructure measurements are available. No uptime or server health is assumed.

03 / THE ENGINEER

Curiosity is
my starting point.

I’m a Computer Systems Technician – Networking student, focused on turning technical concepts into working systems.

My interests span Linux administration, cloud systems, containerization, secure networking, backend deployment, and infrastructure automation. I’m also exploring practical AI tools and how they can support real-world work.

Get my résumé ↓

Cloud & infrastructure

Microsoft Azure · Ubuntu · Linux administration

DevOps & delivery

Docker · Docker Compose · GitHub Actions · Git

Networks & security

WireGuard · Caddy · HTTPS · Networking

Applications & data

Flask · Gunicorn · Backend APIs · PostgreSQL

AI exploration

Practical AI tools · Ongoing learning

04 / WHAT’S NEXT?

Let’s build
something useful.

Have an internship, engineering opportunity, or a project in mind? I’d like to hear about it.

adelekeajayi001@gmail.com ↗

GitHub ↗LinkedIn ↗

Building systems.Moving forward.

Real projects.Practical experience.

Azure cloud portfolio ↗

Secure remote access ↗

API & data services ↗

Versioned delivery ↗

A system, not just a site.