---
title: "David Cletus (@4thman) | Hashnode"
description: "Cloud & DevOps enthusiast passionate about scalable systems, automation, and building sleek web & mobile applications."
url: "https://hashnode.com/@4thman"
---

@4thman

# David Cletus

@4thman · Lagos, Nigeria · Joined May 2026

Cloud & DevOps enthusiast passionate about scalable systems, automation, and building sleek web & mobile applications.

## Comments

[That’s a very fair point. This project focused on the deployment workflow, but in a production environment, I wouldn’t rely on screenshots or a vendor’s report alone. What I would present in a production setup is queryable evidence: container and deployment logs, timestamps, image digests, health and resource metrics, deployment history, and audit records that can be independently checked when an outage or usage dispute occurs. The local flags and health checks help establish what’s running, but production-grade observability and audit trails provide the receipts to verify exactly what ran and when. That distinction is important, and I appreciate the perspective.](https://hashnode.com/posts/dockerizing-a-node-app-shipping-it-to-azure-build-break-fix-ship-3-errors-zero-regrets/6ab715ee33ffa1cbad702101/comment/6ab88b18a6148cbfdbd4b3c2#reply-6ab8e5cd7f6bfcce42b65224)

Reply · Article · Sep 27 · 1 · [Dockerizing a Node App & Shipping It to Azure: Build, Break, Fix & Ship (3 Errors, Zero Regrets) 🐳](https://hashnode.com/posts/dockerizing-a-node-app-shipping-it-to-azure-build-break-fix-ship-3-errors-zero-regrets/6ab715ee33ffa1cbad702101)
