Skip to content

Latest commit

 

History

History
75 lines (46 loc) · 2.33 KB

README.md

File metadata and controls

75 lines (46 loc) · 2.33 KB
Raw

CyberTalents Screen Grabber

✅ This script is tested on mac and linux and windows

✅ Your login credentials are saved in the .env file on your local machine

Script description

This script is created to automate downloading the content from the Cyber Talents platform. It creates a folder for each challenge, take screenshots for each challenge with its writeup and save it in the corresponding folder 🔥🔥

Skip chromium installation "If you have chromium installed already"

export CHROMIUM_EXECUTABLE_PATH=$(which chromium)
export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true

When PUPPETEER_SKIP_CHROMIUM_DOWNLOAD is set to true, puppeteer skips downloading the binaries for chromium, however you must provide an executable path to a chromium binary (which is done via the CHROMIUM_EXECUTABLE_PATH environment variable).

Prepare your machine (if windows machine)

  1. Download Node.js the LTS version then install it. The usual install just next next...

  2. Download Git Bash the windows version and also the usual install. Just tick the option of creating a desktop icon

  3. You should be ready to move to the next step (How to run)

How to run

  1. Clone the repo

    • ssh
      git clone git@github.com:AhmedSaladin/cybertalents-screen-grabber.git

  2. Navigate to the script directory

    cd cybertalents-screen-grabber

  3. Install node modules

    npm i

  4. Add your username to the ".env" file

    echo "CT_USERNAME=your_username" > .env

  5. Add your password to the ".env" file

    echo "CT_PASSWORD=your_password" >> .env

  6. Run the script and let the magic begin 🎩🎩🔥🔥

    npm start

Showcase 🤓

This script is mainly based on web scraping 🕷🕸 and DOM manipulation. Here is a demo of its use.

showcase.mp4

Contribution 👀

This script is created for personal use but made public so if anyone wants to use it can use it. You might face some bugs or not handled errors, you can fix it and create a pull request or you can post a new issue in the issues section and I will fix it whenever I have the time.