Staging instance, all changes can be removed at any time

Skip to content

docker/conf: Use reverse proxy URLs to reach remote SWH services

Antoine Lambert requested to merge anlambert/swh-environment:docker-use-swh-services-reverse-proxy into master

Instead of using a direct access URL to reach a remote SWH service, prefer to use its reverse proxy URL powered by nginx.

It makes the whole docker environment more stable by avoiding connection errors when multiple clients query the same service in an intensive manner.

When testing the listing and loading of package manager origins that produce quite a lot of objects to archive and processed, I observed connection errors in different services, notably in journal clients that made them crash. So align services configuration with production settings and connect to services through their reverse proxies instead.

All tests are still passing after these changes.

Merge request reports