Permalink
Browse files

Use bundle exec cont.

  • Loading branch information...
1 parent fa5e8f2 commit bb96f87b263ac5004f2367c1c02f98103a7d1e39 @joneslee85 joneslee85 committed Sep 21, 2012
View
@@ -40,8 +40,8 @@ Deploying
To deploy the normal guides:
- $ cap deploy
+ $ bundle exec cap deploy
To deploy edge guides:
- $ cap deploy -S edge=true
+ $ bundle exec cap deploy -S edge=true
@@ -97,7 +97,7 @@ h4. Testing
You can test your extensions in the manner you're accustomed to with a standard rails application
<shell>
-$ rake test_app
+$ bundle exec rake test_app
$ bundle exec rspec spec
</shell>
@@ -149,13 +149,13 @@ $ bundle install
If your extension has any migrations, they can be copied over from the extension into your application (along with any other migrations from other railties) by running this command:
<shell>
-$ rake railties:install:migrations
+$ bundle exec rake railties:install:migrations
</shell>
To run those migrations, run this command:
<shell>
-$ rake db:migrate
+$ bundle exec rake db:migrate
</shell>
That's it! Your store should be ready to go with your new custom extension.
@@ -525,8 +525,8 @@ $ bundle install
Now that the extension is setup it's time to install (and then run) the migrations.
<shell>
-$ rake railties:install:migrations
-$ rake db:migrate
+$ bundle exec rake railties:install:migrations
+$ bundle exec rake db:migrate
</shell>
That's it! Your store should be ready to go with your new custom extension.
View
@@ -154,7 +154,7 @@ h4. Refreshing the Default Locale
The default Spree locale is actually maintained as part of the Spree project (and not part of +spree_i18n+ project.) A copy of the default locale information is, however, available in the +spree_i18n+ source. Before you run any of the other rake tasks, its a good idea to "refresh" the localization information for +en.yml+.
<shell>
-$ rake spree_i18n:update_default
+$ bundle exec rake spree_i18n:update_default
</shell>
This updates the localization files in the +default+ directory with the latest information from the Spree project.
@@ -164,7 +164,7 @@ h4. Checking the Translation Progress
The Spree localization files are essentially a continual work in progress. Over time new localization entries are added to the default locale and the translation files need to be updated. You can get a sense for how much translation work is needed using the rake task designed for this purpose.
<shell>
-$ rake spree_i18n:stats
+$ bundle exec rake spree_i18n:stats
</shell>
This will list all of the available locales and give you the percentage of completion for each.
@@ -176,7 +176,7 @@ h4. Syncing the Locales
As new translation strings are added to Spree you will want to resync the locale files so that they provide "stub" entries for these strings which will help to identify them as needing translation. There is a special Rake task that will resync all of the locale files with the latest values from the Spree project. The Rake task will also reorder the translations alphabetically.
<shell>
-$ rake spree_i18n:sync
+$ bundle exec rake spree_i18n:sync
</shell>
NOTE: Remember to run +rake spree_i18n:update_default+ first if you haven't done so already.
@@ -186,7 +186,7 @@ h4. Adding a New Locale
Its simple enought to add a new locale using the appropriate Rake task.
<shell>
-$ rake spree_i18n:new LOCALE=es-PE
+$ bundle exec rake spree_i18n:new LOCALE=es-PE
</shell>
This will generate a new localization with the file name +es-PE.yml+ in the +config/locales+ directory. Here's a snippet of the file that is generated:
@@ -106,11 +106,11 @@ h4. Upgrade Migrations and Assets
The gems that comprise Spree contain various public assets (images, stylesheets, etc.) as well as database migrations that are needed in order to run Spree. There is a Rake tasks designed to copy over the necessary files.
<shell>
-$ rake spree:install
+$ bundle exec rake spree:install
</shell>
Once the migrations are copied over you can migrate using the familiar Rake task for this.
<shell>
-$ rake db:migrate
+$ bundle exec rake db:migrate
</shell>
@@ -13,8 +13,8 @@ h3. Database Migrations
There are several new database changes in the 0.40.0 release. You will need to update your database migrations as follows:
<shell>
-$ rake spree:install:migrations
-$ rake db:migrate
+$ bundle exec rake spree:install:migrations
+$ bundle exec rake db:migrate
</shell>
WARNING: Always be sure to perform a complete database backup before performing any operations. It is also suggested that you examine the new migrations closely before running them so you are aware of what changes are being made to your database.
@@ -15,8 +15,8 @@ h3. Database Migrations
There is only one minor database changes in the 0.50.0 release. You will need to update your database migrations as follows:
<shell>
-$ rake spree:install:migrations
-$ rake db:migrate
+$ bundle exec rake spree:install:migrations
+$ bundle exec rake db:migrate
</shell>
WARNING: Always be sure to perform a complete database backup before performing any operations. It is also suggested that you examine the new migrations closely before running them so you are aware of what changes are being made to your database.
@@ -128,7 +128,7 @@ To prevent problems later please ensure that you've copied all the migrations fr
You can check that all Spree migrations are copied by running:
-<shell> $ rake spree:install:migrations</shell>
+<shell> $ bundle exec rake spree:install:migrations</shell>
Each extension will provide it's own rake task (or generator) for copying migrations so please refer to the extensions README for instructions.

0 comments on commit bb96f87

Please sign in to comment.