Skip to content

Instantly share code, notes, and snippets.

View derekcollison's full-sized avatar

Derek Collison derekcollison

View GitHub Profile
~> telnet 127.0.0.1 4222
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
INFO {"server_id":"bae2f058b327a4b5ecff44407f","host":"0.0.0.0","port":4222,"version":"0.4.22","auth_required":false,"ssl_required":false,"max_payload":1048576}
sub foo 1
+OK
pub foo 2
hi
+OK
@derekcollison
derekcollison / gist:1079547
Created July 13, 2011 01:15
Utilizing crash instance ids for the `vmc files` command
~/Development/vcap/apps/crash_foo> vmc push foo
Would you like to deploy from the current directory? [Yn]:
Application Deployed URL: 'foo.cloudfoundry.com'?
Detected a Sinatra Application, is this correct? [Yn]:
Memory Reservation [Default:128M] (64M, 128M, 256M, 512M, 1G or 2G)
Creating Application: OK
Would you like to bind any services to 'foo'? [yN]:
Uploading Application:
Checking for available resources: OK
@derekcollison
derekcollison / Cloud Foundry Production Updates
Created April 16, 2011 17:11
How to update your application in Cloud Foundry without dropping user requests..
# vmc update is great for test and development, however it stops your old app and stages and starts the new one,
# resulting in dropped requests.
# If you want to update an application without dropping user requests, see below.
# NOTE: This change assumes your application can share services, etc with the new version.
# Assume my app is named foo
vmc push foo-v2 --url foov2.cloudfoundry.com