Add the following to your Gemfile:
gem 'heroku-api'
Put heroku.rb in your jobs folder and add the contents of heroku.html into your layout.
Add the following to your Gemfile:
gem 'heroku-api'
Put heroku.rb in your jobs folder and add the contents of heroku.html into your layout.
--- | |
rvm: | |
- 2.0.0 | |
before_install: | |
- "echo 'gem: --no-document' > ~/.gemrc" | |
- "echo '--colour' > ~/.rspec" | |
- gem install fog | |
- "./script/travis/bundle_install.sh" | |
- export DISPLAY=:99.0 |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
// Start `node d3-server.js` | |
// Then visit http://localhost:1337/ | |
// | |
var d3 = require('d3'), | |
http = require('http') | |
http.createServer(function (req, res) { | |
// Chrome automatically sends a requests for favicons | |
// Looks like https://code.google.com/p/chromium/issues/detail?id=39402 isn't | |
// fixed or this is a regression. |
Flying Widgets adds CSS3 transitions to your dashboard, allowing you to cycle through multiple widget sets on a single TV without page reloads, using stylish CSS3 transitions. You can even still re-order your widgets and save their locations!
Note that sinatra-cyclist is a potential alternative if the machine you use to display your dashboards is lacking in graphics horsepower.
To use, put this file in assets/javascripts/cycleDashboard.coffee. Then find this line in application.coffee:
$('.gridster ul:first').gridster
#!/usr/bin/env ruby | |
# encoding: utf-8 | |
# Brett Terpstra 2013, WTF license <http://www.wtfpl.net/txt/copying/> | |
# Outputs a vertical bar chart from date-based JSON data | |
# Requires the JSON rubygem: `[sudo] gem install json` | |
require 'date' | |
require 'open-uri' | |
require 'rubygems' | |
require 'json' |