21 Apr '13, 6am

Cool trick for leveraging the DNS and proxy power of Pow, with Foreman: I use it to keep dev closer to Heroku prod

January 9, 2013 dancroak dns unix http Foreman as process manager, Pow as DNS server and HTTP proxy Web app development/production parity can be improved by defining process types in a manifest named Procfile such as this one for a Rails app: web: bundle exec rails server thin -p $PORT -e $RACK_ENV In production, Heroku’s Cedar stack reads process types from that file. In development, Foreman manages output streams, responds to crashed processes, and handles user-initiated restarts and shutdowns. One downside to Foreman is typing http://localhost:3000 , http://localhost:3100 , etc. into the web browser, incrementing the port number for each app, forgetting which port is which app. Pow solves this elegantly and is easy to install and maintain. Pow has a DNS server , capable of port proxying to Rack apps. Install and run Pow: curl get.pow.cx | sh Configure Foreman to always ...

Full article: http://robots.thoughtbot.com/post/40110176152/foreman-as-...

Tweets

@mdaisuke

edgeguides.rubyonrails.org 28 Apr '13, 9am

def start url = "#{options[:SSLEnable] ? 'https' : 'http'}://#{options[:Host]}:#{options[:Port]}" puts "=> Booting #{Activ...