Skip to content

Instantly share code, notes, and snippets.


Tim Sabat tsabat

View GitHub Profile
Last active Feb 12, 2018
Vagrant snippet to set VirtualBox guest CPU count to the number of host cores on Linux or OS X (broken 2018)
View Gemfile
gem 'concurrent'
aliang / mymodel.rb
Created Jun 13, 2011
render from model in Rails 3
View mymodel.rb
# yes, sometimes you need to do this. you get pilloried in a forum if you
# ask about it, though!
# this code taken from
class MyModel < ActiveRecord::Base
# Use the my_models/_my_model.txt.erb view to render this object as a string
def to_s
tsabat /
Created Feb 22, 2014
delete unused ebs volumes
#! env python
from boto import ec2
conn = ec2.connect_to_region('us-west-2')
vols = conn.get_all_volumes(filters={'status': 'available'})
for vol in vols:
print 'checking vol:',, 'status:', vol.status, 'attachment_id:', vol.attach_data.status
sinisterchipmunk / LICENSE
Last active Jun 22, 2021
tar, gzip, and untar files using ruby in memory without tempfiles
Copyright (C) 2011 by Colin MacKenzie IV
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
lwe / brew-services.rb
Created Jan 5, 2011
External script for homebrew to simplify starting services via launchctl, out of the box support for any formula which implements #startup_plist.
View brew-services.rb
#!/usr/bin/env ruby -w
# brew-services(1) - Easily start and stop formulas via launchctl
# ===============================================================
# [<sudo>] `brew services` `list`<br>
# [<sudo>] `brew services` `restart` <formula><br>
# [<sudo>] `brew services` `start` <formula> [<plist>]<br>
kentbrew /
Last active Oct 11, 2021
How I Got Node.js Talking on EC2's Port 80

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80: