If you run an active website with lots of new content every day, it's often helpful to keep your local database up-to-date with your production database, so when you're working on the application locally you're working with fresh content.
Here are a couple rake tasks that you can copy-and-paste into your local Rails application which will make this syncing process a one-step process.
| module ApplicationHelper | |
| # ==== Examples | |
| # glyph(:share_alt) | |
| # # => <i class="icon-share-alt"></i> | |
| # glyph(:lock, :white) | |
| # # => <i class="icon-lock icon-white"></i> | |
| def glyph(*names) | |
| content_tag :i, nil, class: names.map{|name| "icon-#{name.to_s.gsub('_','-')}" } | |
| end |
| def redirect_back_or_default(default) | |
| redirect_to(session[:return_to] || default) | |
| session[:return_to] = nil | |
| end | |
| def redirect_referrer_or_default(default) | |
| redirect_to(request.referrer || default) | |
| end |
| # Let's assume you're driving Capybara in both RSpec request specs & Cucumber, | |
| # for example you're using Cucumber as a design/documentation tool, and RSpec | |
| # for the more boring integration tests. | |
| # You don't want to duplicate your click-this-click-that helpers to e.g. | |
| # log_in(username, password). | |
| # You may also have model state setup code which can be shared/reused. | |
| # Where can it go? How can it be loaded? I've been using the following approach: | |
| # |
| #!/bin/bash | |
| if [ "$1" = "-h" -o "$1" = "--help" -o -z "$1" ]; then cat <<EOF | |
| appify v3.0.1 for Mac OS X - http://mths.be/appify | |
| Creates the simplest possible Mac app from a shell script. | |
| Appify takes a shell script as its first argument: | |
| `basename "$0"` my-script.sh |