| #!/usr/bin/env ruby | |
| def output_config | |
| puts <<-END | |
| graph_category App | |
| graph_title passenger status | |
| graph_vlabel count | |
| sessions.label sessions | |
| max.label max processes |
| #!/usr/bin/env ruby | |
| # put in /etc/munin/plugins and restart munin-node | |
| # by Dan Manges, http://www.dcmanges.com/blog/rails-application-visualization-with-munin | |
| # NOTE: you might need to add munin to allow passwordless sudo for passenger-memory-stats | |
| def output_config | |
| puts <<-END | |
| graph_category App | |
| graph_title Passenger memory stats | |
| graph_vlabel count |
| # If you work with git, you've probably had that nagging sensation of not knowing what branch you are on. Worry no longer! | |
| export PS1="\\w:\$(git branch 2>/dev/null | grep '^*' | colrm 1 2)\$ " | |
| # This will change your prompt to display not only your working directory but also your current git branch, if you have one. Pretty nifty! | |
| # ~/code/web:beta_directory$ git checkout master | |
| # Switched to branch "master" | |
| # ~/code/web:master$ git checkout beta_directory | |
| # Switched to branch "beta_directory" |
| <!doctype html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8"/> | |
| <title>Event Pooling, or perhaps Pub/Sub</title> | |
| <script type="text/javascript" charset="utf-8" src="http://ajax.microsoft.com/ajax/jQuery/jquery-1.4.2.min.js"></script> | |
| </head> | |
| <body> | |
| <strong>Who is this?</strong> | |
| <form action="#" method="get" accept-charset="utf-8" id="whoisit"> |
| # Based on | |
| # https://github.com/ng/paperclip-watermarking-app/blob/master/lib/paperclip_processors/watermark.rb | |
| # Modified by Laurynas Butkus | |
| module Paperclip | |
| class Watermark < Processor | |
| # Handles watermarking of images that are uploaded. | |
| attr_accessor :format, :whiny, :watermark_path, :position | |
| def initialize file, options = {}, attachment = nil |
(a gist based on the old toolmantim article on setting up remote repos)
To collaborate in a distributed development process you’ll need to push code to remotely accessible repositories.
This is somewhat of a follow-up to the previous article setting up a new rails app with git.
Set up the new bare repo on the server:
| // $('img.photo',this).imagesLoaded(myFunction) | |
| // execute a callback when all images have loaded. | |
| // needed because .load() doesn't work on cached images | |
| // Modified with a two-pass approach to changing image | |
| // src. First, the proxy imagedata is set, which leads | |
| // to the first callback being triggered, which resets | |
| // imagedata to the original src, which fires the final, | |
| // user defined callback. |
by Jonathan Rochkind, http://bibwild.wordpress.com
Capistrano automates pushing out a new version of your application to a deployment location.
I've been writing and deploying Rails apps for a while, but I avoided using Capistrano until recently. I've got a pretty simple one-host deployment, and even though everyone said Capistrano was great, every time I tried to get started I just got snowed under not being able to figure out exactly what I wanted to do, and figured I wasn't having that much trouble doing it "manually".
| <?php | |
| $categories = get_the_category(); | |
| // Assemble a tree of category relationships | |
| // Also re-key the category array for easier | |
| // reference | |
| $category_tree = array(); | |
| $keyed_categories = array(); |
| Copyright (c) 2011 ZURB, http://www.zurb.com/ |
