Suggestion: Split up the Dockerfile about domain-scan HOT 5 CLOSED

Also, reached out to see if the architecture motivation/overview/instructions are written down somewhere:

https://twitter.com/aidanfeldman/status/738376676619505664

from domain-scan.

Having multiple languages in a single Dockerfile is an antipattern (IMHO), and I think the setup for each scanner could be a lot simpler if you isolated each tool to its own Dockerfile.

@afeld I agree so very wholeheartedly.

cc @garrettr as well

from domain-scan.

We talked about this suggestion at length in Slack, but just wanted to give a picture of what the Dockerfiles might look like, to hopefully better demonstrate the idea/benefits:

# Dockerfile-domain-scan
FROM python:3
CMD glue-code-that-calls-docker-run-on-the-others.py

# Dockerfile-sslyze
FROM python:2
RUN wget ...
CMD sslyze

# Dockerfile-inspect
FROM ruby
RUN bundle install
CMD inspect

...

from domain-scan.

Hacked on this a bit tonight: #67

from domain-scan.

Closing as inactive.

from domain-scan.