Nginx Configuration #
NewsFeed uses a custom Nginx container that serves as a reverse proxy for the frontend and backend services, as well as hosting the documentation site.
Overview #
The Nginx configuration is defined in nginx/proxy.conf
and is used to:
- Serve the documentation site at
/docs/
- Proxy API requests to the backend service
- Proxy all other requests to the frontend service
- Serve thumbnail images from a shared volume
Key Features #
- Built-in documentation: Documentation is built directly in the Dockerfile using multi-stage builds
- Performance optimizations: Increased worker connections, file descriptors, and TCP optimizations
- Security enhancements: Runs as non-root user, includes security headers
Running as Non-Root User #
For security reasons, the Nginx container runs as the nginx
user (non-root). This requires some special configuration:
- Log files are stored in
/tmp/
instead of/var/log/nginx/
- The PID file is stored in
/tmp/nginx.pid
instead of/var/run/nginx.pid
- Appropriate permissions are set for these directories in the Dockerfile
This configuration helps improve security by reducing the privileges of the Nginx process.
Simplified Build Process #
The Nginx image uses a multi-stage build process defined in nginx/Dockerfile
. This approach:
- Uses Hugo in the first stage to build the documentation
- Uses Nginx in the second stage with the pre-built documentation
- Is automatically built as part of the Docker Compose workflow
To build the Nginx image:
# Build using docker compose
docker compose build nginx
# Or build directly with docker
docker build -t newsfeed-nginx -f nginx/Dockerfile .
Configuration Details #
Proxy Configuration #
The main proxy configuration in nginx/proxy.conf
defines how requests are routed:
# Serve documentation
location /docs/ {
alias /docs/public/;
index index.html;
autoindex off;
add_header Cache-Control "public, max-age=3600";
}
# Serve thumbnails as static files
location /thumbnails/ {
alias /thumbnails/;
add_header Cache-Control "public, max-age=86400";
try_files $uri =404;
}
# Proxy /api to backend
location /api/ {
proxy_pass http://backend/api/;
# ... proxy headers ...
}
# Proxy everything else to frontend
location / {
proxy_pass http://frontend/;
# ... proxy headers ...
}
Performance Optimizations #
The Nginx configuration includes several performance optimizations:
# Performance optimizations
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
client_max_body_size 10M;
gzip on;
gzip_comp_level 6;
gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
Additionally, the Dockerfile increases the worker connections and file descriptors:
RUN echo "worker_rlimit_nofile 65535;" >> /etc/nginx/nginx.conf && \
sed -i 's/worker_connections 1024/worker_connections 4096/' /etc/nginx/nginx.conf
Security Headers #
The configuration includes several security headers:
# Security headers
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
Customization #
To customize the Nginx configuration:
- Edit the
nginx/proxy.conf
file - Rebuild the Nginx image using
docker compose build nginx
- Restart the container
For advanced customization, you may need to modify the nginx/Dockerfile
as well.