Commit dc56951
committed
Fix WordNet service 502 error in production deployment
ISSUE IDENTIFIED:
- Production deployment sets PORT=3005 for WordNet service
- Nginx proxy routes /wordnet to wordnet-service:3005
- But WordNet service was hardcoded to port 3003
- This caused 502 Bad Gateway errors in production
SOLUTION:
- Make WordNet service respect PORT environment variable
- Default to port 3003 for development, use PORT env for production
- Update log messages to show dynamic port
The service now works correctly in both:
- Development: runs on port 3003 (default)
- Production: runs on port 3005 (from PORT env var)
This fixes the 502 error when nginx proxy forwards /wordnet requests.1 parent a9220d2 commit dc56951
2 files changed
Lines changed: 9 additions & 9 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
161 | 161 | | |
162 | 162 | | |
163 | 163 | | |
164 | | - | |
165 | | - | |
166 | | - | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
167 | 167 | | |
168 | 168 | | |
169 | 169 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
511 | 511 | | |
512 | 512 | | |
513 | 513 | | |
514 | | - | |
515 | | - | |
516 | | - | |
517 | | - | |
518 | | - | |
519 | | - | |
| 514 | + | |
| 515 | + | |
| 516 | + | |
| 517 | + | |
| 518 | + | |
| 519 | + | |
0 commit comments