ironmoosedevelopment/moosetracks-proxy repository overview

⁠Overview

This Dockerfile is an on-premise agent that allows for capturing HTTP Traffic into https://moosetracks.app⁠

To capture HTTP Traffic calls to an API such as https://swapi.co/api/people/1 through the on-premise agent, update your domain to call http://swapi-co-<TRAIL ID>.proxy.moosetracks.local/api/people/1 instead. The on-premise agent is useful for capturing calls to localhost or to resources inside of a private network.

⁠How to setup

⁠Docker-Compose

moosetracks.onpremise:
    image: ironmoosedevelopment/moosetracks-proxy
    environment:
      VIRTUAL_HOST: "*.proxy.moosetracks.local"
      DEFAULT_HTTP_SCHEME: "https"
nginx:
    image: jwilder/nginx-proxy
    ports:
      - 80:80
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro

⁠Default HTTP Scheme

The on-premise agent will attempt to connect to the proxied API endpoint over both HTTPS and HTTP before giving up. By default, HTTPS will be tried first, but you can control this behavior to reduce response time by specifying DEFAULT_HTTP_SCHEME to either http or https

⁠If you are running locally

⁠Setting up hosts entries manually

For each domain you want to proxy and for each trail that domain is being captured to, a HOSTS file entry will need to be added like so: 127.0.0.1 swapi-co-<TRAIL ID>.proxy.moosetracks.local

⁠Setting up hosts entries automatically

If you have access to your DNS settings on Windows, we recommend setting up https://github.com/stackia/DNSAgent⁠

Use the following rule in your rules.cfg file:

{
        "Pattern": "^(.*)\.proxy\.moosetracks\.local$",
        "Address": "127.0.0.1"
}