The colleague's second stack is the notes site in ~/notes: proxy on port 8081 and the application api with a health check. The stack is up, api is healthy, yet the site answers 502. Find the leg where the request breaks off and fix the stack so that api stays healthy.
Fix the notes stack
The notes stack in ~/notes is up, yet http://localhost:8081/ answers 502. Make the site answer with api's page while sudo docker compose ps shows api as healthy.
Goals · 0 of 2
- Get the site's requests through to api not done yet
- Keep api healthy not done yet