Skip to content

Instantly share code, notes, and snippets.

@mrrooijen
mrrooijen / Capistrano-Deployment-Recipe.rb
Created July 29, 2009 09:34
a "base" Capistrano Rails Deployment Recipe. Use it to deploy your Rails application. It is also easily expandable. So feel free to grab this Recipe and add your own tasks/customization!
# Guide
# Configure the essential configurations below and do the following:
#
# Repository Creation:
# cap deploy:repository:create
# git add .
# git commit -am "initial commit"
# git push origin master
#
# Initial Deployment:
@wemerson
wemerson / variants_controller.rb
Created October 17, 2009 18:53
Spree Variant Uploads
class Admin::VariantsController < Admin::BaseController
...
#add this to controllers/admin/variants_controller.rb or override in extension
#update directory must exist
UPDATE_DIRECTORY = 'public/updates'
require 'fastercsv'
module ActiveRecord
class Base
def self.random
if (c = count) != 0
find(:first, :offset =>rand(c))
end
end
end
end
@njvitto
njvitto / deploy.rake
Created April 11, 2010 16:56 — forked from RSpace/deploy.rake
Rakefile to deploy and rollback to Heroku in two different environments (staging and production) for the same app
#Deploy and rollback on Heroku in staging and production
task :deploy_staging => ['deploy:set_staging_app', 'deploy:push', 'deploy:restart', 'deploy:tag']
task :deploy_production => ['deploy:set_production_app', 'deploy:push', 'deploy:restart', 'deploy:tag']
namespace :deploy do
PRODUCTION_APP = 'YOUR_PRODUCTION_APP_NAME_ON_HEROKU'
STAGING_APP = 'YOUR_STAGING_APP_NAME_ON_HEROKU'
task :staging_migrations => [:set_staging_app, :push, :off, :migrate, :restart, :on, :tag]
task :staging_rollback => [:set_staging_app, :off, :push_previous, :restart, :on]
@cdmwebs
cdmwebs / database.rake
Created December 20, 2010 10:22
Pull a copy of the latest backup via ssh and restore to dev
require 'net/scp'
namespace :db do
desc 'pull the latest backup & restore locally'
task :restore do
Rake::Task['db:download'].invoke
Rake::Task['db:replace'].invoke
end
desc 'pull down the lastest backup from production'
# First configure your models to use Amazon s3 as storage option and setup the associated S3 config.
# Then add the classes your want to migrate in the klasses array below.
# Then run rake paperclip_migration:migrate_to_s3
# Should work but this is untested and may need some tweaking - but it did the job for me.
namespace :paperclip_migration do
desc "migrate files from filesystem to s3"
task :migrate_to_s3 => :environment do
klasses = [:product] # Replace with your real model names. If anyone wants to this could be picked up from args or from configuration.
klasses.each do |klass_key|
@amw
amw / database.yml
Created December 21, 2010 16:12
Standard rails database.yml with additional definition of live database
development:
adapter: mysql2 # must =~ /mysql/
database: adamDb # required
username: your_user
password: keep_secret
live:
ssh_user: # optional, use if live system user differs from your dev user
host: example.com # required, can be IP
adapter: mysql2 # must =~ /mysql/
@silviorelli
silviorelli / config.ru
Created April 8, 2011 10:30
config.ru for using POW Rack server with Rails 2
# Rails.root/config.ru
require "./config/environment"
run ActionController::Dispatcher.new
@jlindley
jlindley / config.ru
Created April 18, 2011 17:03
Rails 2.3.x config.ru (to allow using http://pow.cx/ )
require "./config/environment"
use Rails::Rack::LogTailer
use Rails::Rack::Static
run ActionController::Dispatcher.new
@jhowarth
jhowarth / login.js
Created April 27, 2011 23:08
How to post data to create a new Devise session through ajax
function login() {
var email = $('#user_email').val();
var password = $('#user_password').val();
var data = {remote: true, commit: "Sign in", utf8: "✓",
user: {remember_me: 1, password: password, email: email}};
$.post('/users/sign_in.json', data, function(resp) {
if(resp.success) {
// process success case
} else {
// let the user know they failed authentication