Skip to content
Branch: master
Go to file

Latest commit


Failed to load latest commit information.
Latest commit message
Commit time

To install and start the Pulse frontend

  • First clone this repository: git clone
  • cd docker-pulse
  • In docker-compose.yml you might want to remove the line containing - nginx-load-balancer listed in the networks section of the c-pulse service as well as the last three lines (shown below) as they are specific to our setup and not needed for general usage:
      name: docker_nginx-load-balancer
  • Then clone its dependencies:
    • clone Pulse: git clone
    • clone domain-scan: git clone
    • clone pshtt: git clone
  • This repository is currently in development so not everything is automated. Before starting you need to edit .pulse-env to change the three /home/projects occurrences to the path where you cloned this repository.
  • docker-compose build
  • docker-compose up -d c-pulse

To run a new scan on domains

  • edit pulse/meta.yml to update domains_url to point to a URL with a CSV containing the domains to scan; this CSV is currently required to have the following 3 columns in this order: Domain Name,Domain Type,Agency
  • run docker exec dockerpulse_c-pulse_1 python -m data.update --scan=here
  • once finished, restart docker-compose restart

Some background information as to why you need to clone the three repositories above

Pulse uses domain-scan and expects it to use ssllabs-scan, sslyze and pshtt. domain-scan's Dockerfile includes ssllabs-scan and sslyze, so we do not need to install them. It does not install pshtt though, so we do need to build it ourselves and provide the correct environment variable to run it (which we do using .pulse-env).


Dockerized version of Pulse



No releases published

Sponsor this project

Learn more about GitHub Sponsors
You can’t perform that action at this time.