CHAPTER 04 / CLOUD ENGINEERING
Beyond Localhost
From files on a machine to applications with routes, data and boundaries.
← All chaptersRONNYDONKOR.COM / CLOUDFLARE WORKERS
LIVE$ git status Source is kept in a separate private repository. Original Still Becoming history preserved.
Select a stage to inspect what happens there. The diagrams describe this site; they are not a live feed from Cloudflare.
INSIDE THE WORK / TECHNICAL EVIDENCE
From source to a running site.
Open the evidence below to see the configuration, decisions, and verification behind the work.
01 / HELLO WORLDDeployment receipt
Release: ronnydonkor.com Result: deployment succeeded Build: 19 standalone HTML pages Hosting: my Cloudflare Workers account Access: public, no sign-in
The live portfolio is served directly by my Cloudflare Worker. The homepage and every chapter were checked in the browser after the domain cutover.
02 / CONFIGURATIONWhat gets deployed
Worker: ronny-donkor-portfolio Runtime: Cloudflare Workers Origin: ronnydonkor.com Assets: allowlisted HTML, CSS, JS, images External runtime dependencies: none
The release contains the generated pages, CSS, JavaScript and optimized images. Source scripts, Git history and private configuration are excluded.
03 / DOMAIN & SECURITYA direct path to the site
ronnydonkor.com → owner Cloudflare Worker www → HTTPS apex redirect No account required to view public pages Secrets and private source excluded
The website is static. There is no customer database, payment flow or public administration endpoint in this portfolio.
04 / VALIDATIONSecurity checks you can read
GET → asset + security headers HEAD → headers, no response body POST → 405 before asset access Source/config paths → 404 Unknown route → retains 404
These five Worker checks run against the local response handler. They validate code behavior, not deployed enforcement by every host.
Read the current test transcript ↗