mevansam

#!/bin/bash

if [ -z $1 ] || [ -z $2 ]; then
  echo -e "\nusage: ./ostest.sh <start> <end> [ <image> <user> <key_pair> <private_network> <public_network> ]\n"
  echo -e "  Runs tests numbered from <start> to <end>. Arguments <image>, <user>, <key_pair>,"
  echo -e "  <private_network> and <public_network> are optional but must provided as one. If"
  echo -e "  they are not provided then 'cirros-0.3.3', 'cirros', '$(whoami)' 'private01' and "
  echo -e "  'public01' will be used.\n"
  exit 1
fi

ihuston

Simple Python Flask app on Cloud Foundry

This is a (very) simple Flask application that shows how the built-in Python buildpack detection on Cloud Foundry works.

To push to Cloud Foundry, log in and then use

$ cf push myapp-name

Python on Cloud Foundry

leesmith

https://www.pivotaltracker.com/help/api?version=v3#github_hooks
https://www.pivotaltracker.com/help/api?version=v3#scm_post_commit_message_syntax

SCM Post-Commit Message Syntax

To associate an SCM commit with a specific Tracker story, you must include a special syntax in the commit message to indicate one or more story IDs and (optionally) a state change for the story. Your commit message should have square brackets containing a hash mark followed by the story ID. If a story was not already started (it was in the "not started" state), a commit message will automatically start it. For example, if Scotty uses the following message when committing SCM revision 54321:

  [#12345677 #12345678] Diverting power from warp drive to torpedoes.