Skip to content

docs: fix nginx config mount path in DEPLOYMENT_DOCKER.md SSL example#188

Open
andrerfneves wants to merge 1 commit into
mainfrom
maintenance/fix-docker-nginx-mount-path-20260616
Open

docs: fix nginx config mount path in DEPLOYMENT_DOCKER.md SSL example#188
andrerfneves wants to merge 1 commit into
mainfrom
maintenance/fix-docker-nginx-mount-path-20260616

Conversation

@andrerfneves

@andrerfneves andrerfneves commented Jun 16, 2026

Copy link
Copy Markdown
Owner

Summary

Fixes the nginx config mount path in the DEPLOYMENT_DOCKER.md SSL/TLS production docker-compose example.

Why

The production example mounted ./nginx.conf as /etc/nginx/nginx.conf (the main nginx config file). However, the repo's nginx.conf starts with server { — it is a server block intended for the sites-enabled directory (/etc/nginx/conf.d/default.conf), not a standalone nginx configuration.

A developer following the example verbatim would encounter:

nginx: [emerg] "server" directive is not allowed here in /etc/nginx/nginx.conf:1

This happens because the main nginx config file requires events {} and http {} wrapper blocks around server blocks.

Changes

  • DEPLOYMENT_DOCKER.md: Changed ./nginx.conf:/etc/nginx/nginx.conf to ./nginx.conf:/etc/nginx/conf.d/default.conf in the SSL/TLS docker-compose example

Test Plan

  • All 52 existing tests pass
  • No behavior change — documentation-only fix
  • The fix matches how the Dockerfile itself uses the config (COPY nginx.conf /etc/nginx/conf.d/default.conf)

The production docker-compose SSL/TLS example mounted ./nginx.conf as
/etc/nginx/nginx.conf (the main nginx config file). The repo's nginx.conf
starts with `server {` — it is a server block intended for the sites-enabled
directory, not a standalone nginx configuration.

A user who follows the example verbatim would see nginx fail to start with:
  nginx: [emerg] "server" directive is not allowed here

Fix the mount target to /etc/nginx/conf.d/default.conf.
@vercel

vercel Bot commented Jun 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lightning-decoder Ready Ready Preview, Comment Jun 16, 2026 10:05am

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b21fd4c7cb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread DEPLOYMENT_DOCKER.md
- "443:443"
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf
- ./nginx.conf:/etc/nginx/conf.d/default.conf

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Mount a proxy/TLS config instead

In this SSL/TLS Compose example, this line now loads the repo’s app-serving nginx.conf into the separate nginx:alpine reverse-proxy container. That config only listens on port 80 and serves /usr/share/nginx/html locally, with no proxy_pass to the lightning-decoder service and no listen 443 ssl, so following this production example still will not terminate TLS or route traffic to the app despite mapping 443 and declaring depends_on. The mounted file here needs to be an actual TLS reverse-proxy config rather than the Dockerfile’s static-site config.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant