Install and Configure Spree Commerce 1.2
- Uncomment
gem 'therubyracer', :platforms => :ruby
in Gemfile
-
Default gateways: no (we’ll be installing it ourselves)
-
Default authentication: yes
-
Migrations: yes
-
Seed data: yes
-
Sample data: yes
-
Default admin and password
-
Change spree gem to
gem 'spree', github: 'spree/spree', branch: '1-2-stable'
in Gemfile -
Add
gem 'spree_gateway', github: 'spree/spree_gateway', branch: '1-2-stable'
to Gemfile
-
Test with
bundle exec rails s
-
Ctrl-C
-
Go through commits to old store and apply to new, consolidating as appropriate
-
On live server:
mysqldump -u[user] -p [production_database] > [filename].sql
-
Copy to development server
-
On dev server:
mysql -u[user] [database] < [filename.sql]
(no password needed in my dev environment) -
Go to old store directory, make
config/database.yml
point to new db if necessary -
Upgrade Spree version to latest, following upgrade instructions from Spree. In this case:
-
Gemfile:
-
Bring to rails 3.2.9:
gem 'rails', '3.2.9'
-
Bring to spree latest:
gem 'spree', github: 'spree/spree', branch: '1-2-stable'
-
Update extensions to compatible version
-
-
Test with
bundle exec rails s
-
Export without schema:
mysqldump -u[user] -c -t [database] > [filename.sql]
-
Change to new store project directory
-
Reset db to blank with schema:
-
Import data:
mysql -u[user] [database] <[filename.sql]
(use a new filename each time so you have a data backup) -
Debug any errors (hopefully none)
-
Test with
bundle exec rails s
-
Export data with
mysqldump -u[user] [database] >[filename.sql]
-
Go to production system
-
Make new directory