Skip to content

Commit

Permalink
added comments to base.ini on how to run mitmproxy to observe elastic…
Browse files Browse the repository at this point in the history
…search traffic easily when running locally for dev
  • Loading branch information
dmichaels-harvard committed Nov 22, 2024
1 parent 084b0ce commit 066c501
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions base.ini
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,14 @@ file_wfout_bucket = encoded-4dn-files
# this really shouldn't be used with development, only uncomment if your sure
system_bucket = elasticbeanstalk-encoded-4dn-system
elasticsearch.server = 127.0.0.1:9200
# The elasticsearch.server.actual_port property is useful (only) for running a localhost ElasticSearch
# proxy in order to observe traffic (requests/responses) between portal and ElasticSearch with a tool like
# mitmweb; e.g. setting elasticsearch.server.actual_port to 9201 and elasticsearch.server to localhost:9200
# will case ElasticSearch to actually run on port 9201 but will cause portal to talk to it via port 9200,
# and then we can run mitmweb --mode reverse:http://localhost:9201 -p 9200 --web-port 8081 which will
# allow us to browse to http://localhost:8081 locally to observe all of the ElasticSearch traffic;
# and note to install mitmweb do: pip install mitmproxy
# elasticsearch.server.actual_port = 9201
ontology_path = %(here)s/ontology.json
aws_ip_ranges_path = %(here)s/aws-ip-ranges.json
#this is to reroute downloads to something other than aws s3
Expand Down

0 comments on commit 066c501

Please sign in to comment.