dnordstrom

Sites
 > rvm gemset create spree

Sites
 > rvm gemset use spree

Sites
 > mkdir spree_test

Sites

dnordstrom

source :rubygems

gem 'spree', :path => '../_gems/spree'

dnordstrom

source 'http://rubygems.org'

gem 'rails', '3.1.3'

# Bundle edge Rails instead:
# gem 'rails',     :git => 'git://github.com/rails/rails.git'

gem 'sqlite3'
gem 'spree', :path => '../_gems/spree'

dnordstrom

require 'migraine'

migration = Migraine::Migration.new(
  from: 'mysql://root:root@localhost/migraine_from',
  to: 'mysql://root:root@localhost/migraine_to'
)

migration.map 'addresses' => 'spree_addresses'
  map 'id'
  map 'firstname'

dnordstrom

require 'migraine'

migration = Migraine::Migration.new(
  from: 'mysql://root:root@localhost/migraine_from',
  to: 'mysql://root:root@localhost/migraine_to'
)

migration.prefix 'spree_'
migration.generate 'migrate.rb'

dnordstrom

require 'migraine'

migration = Migraine::Migration.new(
  from: 'mysql://root:root@localhost/migraine_from',
  to: 'mysql://root:root@localhost/migraine_to'
)

migration.prefix 'spree_'
migration.generate 'generated.rb'

dnordstrom

# This file is auto-generated from the current state of the database. Instead of editing this file, 
# please use the migrations feature of Active Record to incrementally modify your database, and
# then regenerate this schema definition.
#
# Note that this schema.rb definition is the authoritative source for your database schema. If you need
# to create the application database on another system, you should be using db:schema:load, not running
# all the migrations from scratch. The latter is a flawed and unsustainable approach (the more migrations
# you'll amass, the slower it'll run and the greater likelihood for issues).
#
# It's strongly recommended to check this file into your version control system.

dnordstrom

# encoding: UTF-8
# This file is auto-generated from the current state of the database. Instead
# of editing this file, please use the migrations feature of Active Record to
# incrementally modify your database, and then regenerate this schema definition.
#
# Note that this schema.rb definition is the authoritative source for your
# database schema. If you need to create the application database on another
# system, you should be using db:schema:load, not running all the migrations
# from scratch. The latter is a flawed and unsustainable approach (the more migrations
# you'll amass, the slower it'll run and the greater likelihood for issues).

dnordstrom

-- MySQL dump 10.13  Distrib 5.5.15, for osx10.7 (i386)
--
-- Host: localhost    Database: asgseedbank
-- ------------------------------------------------------
-- Server version	5.5.15

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;

dnordstrom

-- MySQL dump 10.13  Distrib 5.5.15, for osx10.7 (i386)
--
-- Host: localhost    Database: asgseedbank
-- ------------------------------------------------------
-- Server version	5.5.15

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;