search

MI-DPLA / combine

Combine /kämˌbīn/ - Metadata Aggregator Platform
MIT License
26 stars 11 forks source link

Internal vs Public ip's and hosts #334

Closed ghukill closed 4 years ago

ghukill commented 5 years ago

A build on AWS revealed that some network calls to local services -- e.g. ElasticSearch, Livy -- are using the public IP of the Combine machine. A public IP is needed (convenient) if those ports and services should be reachable, but no need for local calls to hit IP. Will be faster avoiding loopback, as well.

Consider adding PUBLIC and INTERNAL prefixes to these settings in localsettings.py to differentiate, then confirm the appropriate ones are used in Combine.

ghukill commented 5 years ago

Possible overlap with #310?

antmoth commented 4 years ago

Fixed in docker deployment