Customer decided paying was optional, this project is two years old (2022) and has some questionable code in it.

Customise .env-example then run docker.

Apparently I didn't know how to use chmod, hence permissions issues on the certificates.....

Backend of ScanSearch created 11/13/2022

• Send out emails for price drops
• Work on api URLs // Future versions

• Description
• How To Use
• License

Backend api that essentially acts as a reverse proxy to SerpAPI and mushes with Javascript front-end ( To be coded)

• Price comparison for clothing
• Mailchimp notifications on price drops
• TBS customisation on second request

docker build . -t {dockerusername}/scansearch

docker run -d -v ~/cert:/etc/letsencrypt/live/{yourdomain}/ -p 443:443 -p 80:80 {dockerusername/repo}

Use letsencrypt to get https signatures, then move to ~/cert ( Will remove auto-renew feature, but sorts out docker not having permission to read certificates) Alternatively you could add docker to the permission group that can read /etc/letsencrypt etc. But I have not added this yet

Add .env file, add following lines: serpapi={apikey}

    // Add options here

Do not care