spree 0.70.3 → 0.70.4

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.

This version of spree might be problematic. Click here for more details.

Files changed (4) hide show
  1. data/README.md +3 -12
  2. data/lib/spree/templates/extension/Rakefile +5 -0
  3. data/lib/spree/templates/extension/extension.gemspec +1 -0
  4. metadata +22 -22
data/README.md CHANGED
@@ -44,15 +44,6 @@ If you also want some sample products, orders, etc. to play with you can run the
44
44
 
45
45
  $ bundle exec rake spree_sample:load
46
46
 
47
- Peformance
48
- ----------
49
-
50
- Rails 3.1 introduced a concept known as the asset pipeline. Unfortunately it results in poor performance when running your site in development mode (production mode is unaffected.) You may want to run the following command when testing locally in development mode
51
-
52
- $ bundle exec rake assets:precompile:nondigest
53
-
54
- Using the precompile rake task in development will prevent any changes to asset files from being automatically included in when you reload the page. You must re-run the precompile task for changes to become available.
55
-
56
47
  Browse Store
57
48
  ------------
58
49
 
@@ -92,15 +83,15 @@ The source code is essentially a collection of gems. Spree is meant to be run w
92
83
  Performance
93
84
  -----------
94
85
 
95
- You may noticed that your Spree store runs slowly in development mode. This is a side-effect of how Rails works in development mode which is to continuous reload your Ruby objects on each request. The introduction of the asset pipeline in Rails 3.1 made default performance in development mode significantly worse. There are, however, a few tricks to speeding up performance.
86
+ You may noticed that your Spree store runs slowly in development mode. This is a side-effect of how Rails works in development mode which is to continuous reload your Ruby objects on each request. The introduction of the asset pipeline in Rails 3.1 made default performance in development mode significantly worse. There are, however, a few tricks to speeding up performance in development mode.
96
87
 
97
88
  You can recompile your assets as follows:
98
89
 
99
- $ bundle exec rake assets:precompile RAILS_ENV=development
90
+ $ bundle exec rake assets:precompile:nondigest
100
91
 
101
92
  If you want to remove precompiled assets (recommended before you commit to git and push your changes) use the following rake task:
102
93
 
103
- $ bundle exec rake assets:clean
94
+ $ bundle exec rake assets:clean
104
95
 
105
96
 
106
97
 
data/lib/spree/templates/extension/Rakefile CHANGED
@@ -2,6 +2,11 @@ require 'rake'
2
2
  require 'rake/testtask'
3
3
  require 'rake/packagetask'
4
4
  require 'rubygems/package_task'
5
+ # If this extension was generated from inside an application,
6
+ # then you *must* specify the rspec-rails and cucumber-rails gems as dependencies
7
+ # for that application, otherwise these files will not be found.
8
+ #
9
+ # Alternatively, place a Gemfile inside the extension directory which specifies these gems as dependencies
5
10
  require 'rspec/core/rake_task'
6
11
  require 'cucumber/rake/task'
7
12
  require 'spree_core/testing_support/common_rake'
data/lib/spree/templates/extension/extension.gemspec CHANGED
@@ -19,5 +19,6 @@ Gem::Specification.new do |s|
19
19
 
20
20
  s.add_dependency 'spree_core', '>= <%= Spree.version %>'
21
21
  s.add_development_dependency 'rspec-rails'
22
+ s.add_development_dependency 'sqlite3'
22
23
  end
23
24
 
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: spree
3
3
  version: !ruby/object:Gem::Version
4
- hash: 257
4
+ hash: 271
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 70
9
- - 3
10
- version: 0.70.3
9
+ - 4
10
+ version: 0.70.4
11
11
  platform: ruby
12
12
  authors:
13
13
  - Sean Schofield
@@ -15,7 +15,7 @@ autorequire:
15
15
  bindir: lib/spree/bin
16
16
  cert_chain: []
17
17
 
18
- date: 2011-11-22 00:00:00 Z
18
+ date: 2012-03-04 00:00:00 Z
19
19
  dependencies:
20
20
  - !ruby/object:Gem::Dependency
21
21
  version_requirements: &id001 !ruby/object:Gem::Requirement
@@ -23,12 +23,12 @@ dependencies:
23
23
  requirements:
24
24
  - - "="
25
25
  - !ruby/object:Gem::Version
26
- hash: 257
26
+ hash: 271
27
27
  segments:
28
28
  - 0
29
29
  - 70
30
- - 3
31
- version: 0.70.3
30
+ - 4
31
+ version: 0.70.4
32
32
  requirement: *id001
33
33
  type: :runtime
34
34
  prerelease: false
@@ -39,12 +39,12 @@ dependencies:
39
39
  requirements:
40
40
  - - "="
41
41
  - !ruby/object:Gem::Version
42
- hash: 257
42
+ hash: 271
43
43
  segments:
44
44
  - 0
45
45
  - 70
46
- - 3
47
- version: 0.70.3
46
+ - 4
47
+ version: 0.70.4
48
48
  requirement: *id002
49
49
  type: :runtime
50
50
  prerelease: false
@@ -55,12 +55,12 @@ dependencies:
55
55
  requirements:
56
56
  - - "="
57
57
  - !ruby/object:Gem::Version
58
- hash: 257
58
+ hash: 271
59
59
  segments:
60
60
  - 0
61
61
  - 70
62
- - 3
63
- version: 0.70.3
62
+ - 4
63
+ version: 0.70.4
64
64
  requirement: *id003
65
65
  type: :runtime
66
66
  prerelease: false
@@ -71,12 +71,12 @@ dependencies:
71
71
  requirements:
72
72
  - - "="
73
73
  - !ruby/object:Gem::Version
74
- hash: 257
74
+ hash: 271
75
75
  segments:
76
76
  - 0
77
77
  - 70
78
- - 3
79
- version: 0.70.3
78
+ - 4
79
+ version: 0.70.4
80
80
  requirement: *id004
81
81
  type: :runtime
82
82
  prerelease: false
@@ -87,12 +87,12 @@ dependencies:
87
87
  requirements:
88
88
  - - "="
89
89
  - !ruby/object:Gem::Version
90
- hash: 257
90
+ hash: 271
91
91
  segments:
92
92
  - 0
93
93
  - 70
94
- - 3
95
- version: 0.70.3
94
+ - 4
95
+ version: 0.70.4
96
96
  requirement: *id005
97
97
  type: :runtime
98
98
  prerelease: false
@@ -103,12 +103,12 @@ dependencies:
103
103
  requirements:
104
104
  - - "="
105
105
  - !ruby/object:Gem::Version
106
- hash: 257
106
+ hash: 271
107
107
  segments:
108
108
  - 0
109
109
  - 70
110
- - 3
111
- version: 0.70.3
110
+ - 4
111
+ version: 0.70.4
112
112
  requirement: *id006
113
113
  type: :runtime
114
114
  prerelease: false