---
title: "Discussion on \"🚀 DPDzero DevOps Intern Assignment: Nginx Reverse Proxy with Docker Compose\" | Hashnode"
description: "Discussion on \"🚀 DPDzero DevOps Intern Assignment: Nginx Reverse Proxy with Docker Compose\". 👩‍💻 By Divya V. Satpute\n\n📌 Overview\nAs part of the DPDzero DevOps Internship Assignment, I was asked to containerize two services and expose them behind an Nginx reverse proxy using Docker Compose.\nThis blog will help you:\n\nUnderstand the technica..."
url: "https://hashnode.com/posts/dpdzero-devops-intern-assignment-nginx-reverse-proxy-with-docker-compose/685af6cc5b389e6d48b2a48f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [🚀 DPDzero DevOps Intern Assignment: Nginx Reverse Proxy with Docker Compose](https://teacode1122.hashnode.dev/dpdzero-devops-intern-assignment-nginx-reverse-proxy-with-docker-compose?utm_source=hashnode&utm_medium=feed)

👩‍💻 By Divya V. Satpute 📌 Overview As part of the DPDzero DevOps Internship Assignment, I was asked to containerize two services and expose them behind an Nginx reverse proxy using Docker Compose. This blog will help you: Understand the technica...

Jun 24, 2025 · 4 min read · teacode1122.hashnode.dev  
Read the article

-   [#tws](https://hashnode.com/tag/tws)
-   [#assignment-help](https://hashnode.com/tag/assignment-help)
-   [#teacode](https://hashnode.com/tag/teacode)

## Written by

[Divya vasant satpute](https://hashnode.com/@divya1122)

@divya1122 · Chinchwad pune

  
[View profile](https://hashnode.com/@divya1122)

, I'm a seasoned DevOps engineer 🛠️ with a knack for optimizing software development lifecycles and infrastructure operations. 💡 Specializing in cutting-edge DevOps practices and proficient in tools like Docker, Kubernetes, Ansible, and more, I'm committed to driving digital transformation and empowering teams to deliver high-quality software with speed and confidence. 💻

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 4](https://hashnode.com/posts/dpdzero-devops-intern-assignment-nginx-reverse-proxy-with-docker-compose/685af6cc5b389e6d48b2a48f/comment/6aebbf273681c89d6c69ce2f)

Clean internship shape: two app services behind one nginx on a shared compose network. The ops habit that prevents most 502 tickets is resolving upstreams by service name, not by published host ports — leave the app ports internal and expose only 80/443 on the proxy. After a backend recreate, a long-lived nginx worker can keep a stale resolved address unless you reload or recreate the proxy, or use a variable-plus-resolver pattern, so treat upstream DNS churn as part of the deploy checklist.

For the proxy\_pass blocks I keep trailing-slash rules deliberate (join vs strip path), set Host, X-Forwarded-For, and X-Forwarded-Proto so apps build public redirects correctly, and enable proxy\_http\_version 1.1 with an empty Connection header when keepalive to the containers matters. After compose up I exec into the nginx container, resolve each upstream name, hit the service port directly, then through the public vhost — mismatches almost always mean network membership or a path-joining typo, not the image tag itself.