Deployed versions prior to 6/30/2019 (< 3.4.0) might want to do a clean deployment - we're changing from Redis to MongoDB, and it doesn't translate, cleanly. This is able to run locally during development somewhat consistently.
This tool lets you monitor the price of Southwest flights that you've booked. It will notify you if the price drops below what you originally paid. Then you can re-book the same flight and get Southwest credit for the price difference. This tool also lets you monitor the price of all Southwest flights on a given day. It will notify you if any flight on that day drops below the previous cheapest flight.
Note that to send text messages you need a Plivo account and to send emails you'll need a Mailgun account (or SMTP credentials). You can also send discord alerts through a webhook. You can run this tool without these accounts, but you won't get the notifications.
You can log in with either:
admin
and the-admin-password-123
mom
and the-admin-password-123
The second option is nice when giving out access to friends and family since it will only display alerts for the given username. Note that the password is the same for all accounts, and the admin can see all alerts.
When creating alerts, note that the email and phone numbers are optional. If those are both left blank, the user will need to manually log in to view price drops.
Deploy
Heroku Scheduler
from your app's dashboardnpm run task:check
When updates become available, you will have to deploy them yourself using the Heroku CLI. This app follows SemVer in its versioning, so make sure to read the release notes when deploying a major version change.
Note: Deployed versions prior to 4/9/2018 using Mailgun will need to verify constants: MAILGUN_DOMAIN
and MAILGUN_EMAIL
.
Note: Deployed versions prior to 4/28/2018 (< 3.0.0) on Heroku will need to install the buildpack https://github.com/jontewks/puppeteer-heroku-buildpack
Note: Deployed versions prior to 7/21/2018 (< 3.2.0) on Heroku will need to verify the PROXY
constant if you want to use a proxy to make the calls.
Note: Deployed versions prior to 6/30/2019 (< 3.4.0) might want to do a clean deployment - we're changing from Redis to MongoDB, and I don't think it will migrate cleanly (or at all). Otherwise, you'll need to add the mLab MongoDB add-on manually.
Southwest has some very fancy bot protections in place.
CHROME_DEBUG=true DEBUG="puppeteer:*"
combined with node inspect
to debug strange chrome issues.
slowmo
is enabled and headless
is disabledhttps://infosimples.github.io/detect-headless
will be opened before a Southwest URLInstructions on deploying a proxy is outside the scope of this project. However, here's some information about proxies that might be useful:
squid.conf
with something like this to prevent someone from using your setup as an open proxy:acl swa dstdomain .southwest.com
http_access allow swa
http_access deny all
To configure the Price Drop Bot to use your proxy, define a new PROXY
variable within the Heroku Config. The proxy format should be http://IP:port. Example: heroku config:set PROXY='http://123.123.123.123:1234'
To run the test suite:
yarn test
To run a console loaded up with Alert
and Flight
objects:
yarn console
When debugging chrome/puppeteer issues it's helpful to use the following command:
DEBUG="puppeteer:*" CHROME_DEBUG=true node tasks/check.js
This will send helpful chromium debugging output into your console, switch off headless mode, and enable some additional logging to help debug what might be going wrong.
If you are running into firewall notifications on macos, you'll need to sign the chromium binary:
/usr/bin/find . -name "Chromium.app" | xargs sudo codesign --sign - --force --deep
There are 3 containers in the docker setup:
To run via docker-compose:
Create your .env file from the example. Set the mongo DB url like:
MONGODB_URI="mongodb://mongodb:27017/sw_db"
Then you can start up the docker instance.
docker-compose build
docker-compose up -d
The interface will be available on http://\<dockerhost>:3000
There's a separate docker-compose
and Dockerfile
for the Raspberry Pi. Chrome installation on a raspberry pi device works differently, and it doesn't support mongodb by default.
docker-compose -f docker-compose.pi.yml up -d
This is a fork of minamhere's fork of maverick915's fork of scott113341's original project.
Downstream changes were integrated from:
Thanks to the following for their contributions: