paul
1773ed5f95
Mirror to GitHub / mirror (push) Successful in 26s
Test and Lint / backend-test (push) Successful in 1m11s
continuous-integration/drone/push Build is passing
Test and Lint / frontend-test (push) Successful in 2m28s
Version and Release / version-bump (push) Successful in 32s
Version and Release / trigger-drone (push) Has been skipped
Original: feat: enhance security logging and ensure rate limit blocks are properly tracked - Add comprehensive logging for rate limit blocks with full request details - IP address (with proper proxy detection), user agent, headers, timestamps - Rate limit info (current count, limit, remaining, reset time) - Separate tracking for auth vs general endpoints - Enhance authentication failure logging - JWT validation failures with detailed error info - Admin auth attempts without token - Failed token validation with user context - All events include IP, path, method, user agent - Improve Winston logger configuration for production - Add automatic log rotation (10MB errors, 50MB combined) - Create separate security.log for auth/rate limit events - Ensure logs directory exists automatically - Add structured JSON format for log aggregation - Support container logging with LOG_TO_CONSOLE env var - Create comprehensive documentation - Security logging guide with examples - Monitoring recommendations - Configuration reference - Add test script to verify logging functionality All rate limit settings remain configurable via admin panel: - Window duration, max requests, auth limits - Skip authenticated requests option - Public endpoints only option 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
98 lines
2.8 KiB
Markdown
98 lines
2.8 KiB
Markdown
# Production Deployment Guide
|
|
|
|
This guide explains how to deploy PicPeak in production behind a reverse proxy like Traefik.
|
|
|
|
## Environment Configuration
|
|
|
|
### Frontend Configuration
|
|
|
|
For production deployment behind a reverse proxy (Traefik, Nginx, etc.), the frontend should use relative URLs to automatically inherit the protocol (HTTPS) and domain.
|
|
|
|
1. Copy the production environment template:
|
|
```bash
|
|
cp frontend/.env.production.example frontend/.env.production
|
|
```
|
|
|
|
2. Set the API URL to use relative path:
|
|
```env
|
|
# frontend/.env.production
|
|
VITE_API_URL=/api
|
|
```
|
|
|
|
This ensures all API calls will use the same domain and protocol as the frontend.
|
|
|
|
### Backend Configuration
|
|
|
|
Ensure your backend `.env` file has the correct URLs:
|
|
```env
|
|
# backend/.env
|
|
FRONTEND_URL=https://yourdomain.com
|
|
ADMIN_URL=https://yourdomain.com
|
|
```
|
|
|
|
## Docker Compose Production
|
|
|
|
When using Docker Compose in production:
|
|
|
|
1. Build with production environment:
|
|
```bash
|
|
docker-compose -f docker-compose.prod.yml build --build-arg NODE_ENV=production
|
|
```
|
|
|
|
2. The frontend nginx configuration already includes proper proxy settings for:
|
|
- `/api` → Backend API
|
|
- `/photos` → Protected photo access
|
|
- `/thumbnails` → Thumbnail images
|
|
- `/uploads` → Public uploads (logos, favicons)
|
|
|
|
## Traefik Configuration
|
|
|
|
Example Traefik labels for docker-compose:
|
|
|
|
```yaml
|
|
services:
|
|
frontend:
|
|
labels:
|
|
- "traefik.enable=true"
|
|
- "traefik.http.routers.picpeak.rule=Host(`yourdomain.com`)"
|
|
- "traefik.http.routers.picpeak.entrypoints=websecure"
|
|
- "traefik.http.routers.picpeak.tls.certresolver=letsencrypt"
|
|
- "traefik.http.services.picpeak.loadbalancer.server.port=80"
|
|
```
|
|
|
|
## Important Notes
|
|
|
|
1. **No Hardcoded URLs**: The application uses environment variables with relative URL fallbacks, making it production-ready.
|
|
|
|
2. **HTTPS Only**: When `VITE_API_URL=/api`, all requests will use the same protocol as the page (HTTPS in production).
|
|
|
|
3. **CORS Configuration**: The backend CORS is configured to accept requests from the URLs specified in `FRONTEND_URL` and `ADMIN_URL`.
|
|
|
|
4. **Static Assets**: All static assets (photos, thumbnails, uploads) are served through the nginx proxy, inheriting authentication headers.
|
|
|
|
## Verification
|
|
|
|
After deployment, verify:
|
|
|
|
1. Check browser console for any localhost URLs (there should be none)
|
|
2. Verify all API calls use HTTPS
|
|
3. Check that images load correctly with authentication
|
|
4. Test favicon and logo display
|
|
|
|
## Troubleshooting
|
|
|
|
If you see console errors about localhost:
|
|
|
|
1. Ensure `VITE_API_URL=/api` in frontend environment
|
|
2. Clear browser cache
|
|
3. Rebuild frontend with production environment:
|
|
```bash
|
|
cd frontend
|
|
npm run build
|
|
```
|
|
|
|
If images don't load:
|
|
|
|
1. Check that nginx proxy locations are configured
|
|
2. Verify authentication tokens are being sent
|
|
3. Check backend logs for authentication errors |