From 8d88ba9bc5463fe993a6ea8914fe34c356d88646 Mon Sep 17 00:00:00 2001 From: Ryan Glover Date: Tue, 7 Apr 2015 18:53:41 -0500 Subject: [PATCH] swap Sass packages Replace particle4dev:sass package with fourseven:scss to mitigate issue with former package not working on Windows. This is a blind fix as it hasn't been tested on a Windows machine. The package being introduced as a replacement, however, has noted support for Windows. Fixes #45 --- .meteor/packages | 2 +- .meteor/versions | 2 +- README.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.meteor/packages b/.meteor/packages index a430d2e..a2b74e5 100644 --- a/.meteor/packages +++ b/.meteor/packages @@ -12,7 +12,6 @@ check audit-argument-checks iron:router themeteorchef:jquery-validation -particle4dev:sass@0.3.0 twbs:bootstrap browser-policy meteorhacks:npm @@ -21,3 +20,4 @@ meteorhacks:npm npm-container themeteorchef:bert meteorhacks:ssr +fourseven:scss diff --git a/.meteor/versions b/.meteor/versions index 0008aee..3fdae45 100644 --- a/.meteor/versions +++ b/.meteor/versions @@ -18,6 +18,7 @@ deps@1.0.7 ejson@1.0.6 email@1.0.6 fastclick@1.0.3 +fourseven:scss@2.1.1 geojson-utils@1.0.3 html-tools@1.0.4 htmljs@1.0.4 @@ -50,7 +51,6 @@ npm-bcrypt@0.7.8_2 npm-container@1.0.0 observe-sequence@1.0.6 ordered-dict@1.0.3 -particle4dev:sass@0.3.0 random@1.0.3 reactive-dict@1.1.0 reactive-var@1.0.5 diff --git a/README.md b/README.md index fae460b..e85c2eb 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ For more detail on updates, [read the Changelog](https://github.com/themeteorche - jQuery - `meteor add jquery` - jQuery Validation - `meteor add themeteorchef:jquery-validation` - NPM - `meteor add meteorhacks:npm` -- Sass - `meteor add particle4dev:sass@0.3.0` +- Sass - `meteor add fourseven:scss` - SSR - `meteor add meteorhacks:ssr` - Underscore - `meteor add underscore` @@ -118,7 +118,7 @@ CSS in Base is written using [Sass](http://sass-lang.com). ###### Configuration Base includes a pattern for managing your API keys, connection strings, and other configuration information using two files: `settings-development.json` and `settings-production.json`. This pattern separates your development and production configuration into two separate files for the sake of security. -Per [Josh Owen's article](http://joshowens.me/environment-settings-and-security-with-meteor-js/), it's considered "bad practice" to check your production keys into your repo (private or otherwise). Base accounts for this by giving you two separate files, but also specifies that your `settings-production.json` file should be ignored by git in `.gitignore`. +Per [Josh Owens' article](http://joshowens.me/environment-settings-and-security-with-meteor-js/), it's considered "bad practice" to check your production keys into your repo (private or otherwise). Base accounts for this by giving you two separate files, but also specifies that your `settings-production.json` file should be ignored by git in `.gitignore`. This means that keys that are only used for testing or development purposes can be placed in `settings-development.json`, while keys used in your production application should be placed in `settings-production.json`. Sharing and management of `settings-production.json` should be done on a person-to-person basis and _not_ made globally accessible. -- 2.0.0