A Deployable Service™ that runs scheduled assertions on fetched HTTP content.
#Direct Usage
- Fork bnorton/alive from GitHub to {{username}}
- Rename all instances of
{{username}}
with yours - Create a heroku app with the multi buildpack (to support both the ruby and phantomjs buildpacks)
git clone git@github.com:{{username}}/alive.git
heroku create {{username}}-alive --buildpack https://github.com/ddollar/heroku-buildpack-multi.git
Required:
- Add a MongoDB database =>
heroku addons:create mongohq
- Add a username and password for the new mongo database
- Add a Redis database =>
heroku addons:create heroku-redis:hobby-dev
Optional:
- Add a SendGrid account =>
heroku addons:create sendgrid:starter
- Add a new Incoming WebHook integration to Slack and add the
SLACK_URL
and theSLACK_CHANNEL
to the heroku config - Add a Bugsnag account =>
heroku addons:create bugsnag
heroku config # and grab your mongodb url
heroku config:set RAILS_ENV=production \
RACK_ENV=production \
MONGODB_URL={{mongodb url}} \
REDIS_URL={{redis url}} \
SECRET_KEY_BASE=$(rake secret) \
SLACK_URL={{slack url}} \
SLACK_CHANNEL={{slack channel}} \
BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git
- Deploy your first version with
git push heroku master
- If setting up CircleCI with heroku deployment modify
circle.yml
to have your app-name
To run the RSpec / Capybara tests you'll need:
phantomjs
installedbundle install
(maybegem install bundler
first)rake
runs the existing test suite- Add tests
- Run tests
- Add implementation
- Run tests
- Commit / Push / Pull request
- Isolate the problem logically
- Isolate the problem with a failing test