cunningdj / site-checker

Website serving checker. Alerts via email. Any number of websites, and set the checker interval.

Site Checker

Checks the websites every interval, and sends an email for any websites that are down (status 404 from a GET request on the given url).

Instructions

1. Run npm install in the command line to install the dependencies
2. Copy the json files from src/templates/ to src/.
3. Set up a Gmail (or whichever smtp host) smtp key in Gmail. See Nodemailer and Gmail for instructions (link in notes).
4. Add the Gmail app key to auth.json
5. Fill in the other values in the .json files.
   • Any number of websites can be added to sites.json
6. Run the src/checker.js script with a daemon tool like forever or pm2.

Notes

• If the interval time is very small and a website goes down, you'll get a lot of emails in a short time. Take this into account when deciding an interval time. I've found every 15 minutes to be a reasonable interval for my websites.
• This daemon process lends itself well to a low power server device like Raspberry Pi, or any server you currently have running 24/7.
• The base email functionality is in Nodemailer. See the OAuth2 page for help or retooling.

site-checker's Issues

Read configuration from environment variables

It would be nice if this was set up to read configuration values differently depending on if it is used in development vs production. We use Heroku for a lot of our New Leaf Digital projects. So being able to read from environment variables for the production setup would be nice. Not sure how you'd tell which is set up the app is in. Maybe a JSON file with a property and the value is set to either development or production. Then you just read that to know where to pull the values from. What do you think?