Here's what I did to get things working.
Yep, over at: https://developer.apple.com
* |
Here's what I did to get things working.
Yep, over at: https://developer.apple.com
import json | |
import os | |
import requests | |
GITHUB_TOKEN = os.environ.get('GITHUB_TOKEN') | |
if GITHUB_TOKEN is None: | |
raise Exception('Missing GITHUB_TOKEN from os.environ') |
#! /bin/bash | |
# HEADS UP! Make sure to use '*' or a valid hostname for the FDQN prompt | |
echo 01 > ca.srl | |
openssl genrsa -des3 -out ca-key.pem | |
openssl req -new -x509 -days 365 -key ca-key.pem -out ca.pem | |
openssl genrsa -des3 -out server-key.pem | |
openssl req -new -key server-key.pem -out server.csr |
# This configuration will set up a database (db) and a web server (web) VM. | |
# Assumes the use of VirtualBox 4.3.14-95030 as a provider. | |
# Uses vagrant-vbguest plugin (https://github.com/dotless-de/vagrant-vbguest) | |
# to keep VirtualBox Guest Addition wrangled. | |
# Configuration | |
# Machine-specific configuration | |
DB_INSTALL_SCRIPT = "vagrant_data/db/install.sh" |
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
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
#!/bin/bash | |
# A quick and dirty way to package Graphite using fpm and a custom target. | |
# (c) by Hynek Schlawack, MIT licence, USE AT OWN RISK. | |
# EXECUTE DIRECTLY ON A BUILDBOT -- IT USES REAL PATHS SINCE GRAPHITE IS PRICKY | |
# Necessary Ubuntu dependency for building: build-essential, libcairo-dev and | |
# fpm which isn't packaged unfortunately: https://github.com/jordansissel/fpm |