Repository navigation
docs(c05): Day 06 서비스 스택 분리와 격리 네트워크 설계 — Docker Compose와 Nginx 인그레스 구성 - #97
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
개요
mini-watch/day06)에 대한 기술 블로그 포스트를 발행합니다.m5d1-general)와 관제 서비스(m5d1-monitor)의 2-Compose 스택 분리 및 L2 외부 브리지 공유망(m5d1-events)을 통한 보안 격리 아키텍처를 다룹니다.주요 내용
data-net)에 격리하고, API 컨테이너 간에만 사전 프로비저닝된m5d1-events를 연결하여 무단 접근 차단.limit_except GET { deny all; }지시자를 통해 외부로부터의 위조 감사 로그POST삽입을 차단하고 내부망 전송만 허용.pg_isready기반service_healthy체인과stop_grace_period: 30s를 적용하여 DB 초기화 지연 및 데이터 손상 방어.docker network disconnect를 통한 공유망 단절 결함 격리 검증.COPY레이어 캐시에 따른 단순 재시작(restart)과 재빌드(up -d --build)의 런타임 메커니즘 규명.검증 내역
uv run python pipeline/harness.py docs/posts/c05-mini-watch-day06.md: 모든 거버넌스 및 무결성 검증 통과 (Exit Code 0)npm --prefix blog run build: 138개 전체 페이지 정적 빌드 성공 (Complete!)