A grunt project to create the pebble {code} & pebble.it sites

1. Install node.js, npm, grunt.js, and Sass.

2. Install the sass gem

    gem install sass -v 3.3.0.rc.2
   

3. Install all required packages

    npm i
   

4. Generate the site (only needed once)

    grunt make
   

5. Start dev server & tasks

    grunt
   

If you wish to use liveReload you will need to install & activate the relivant browser extension.

Before being able to deploy, you will need to setup your environmnet, with

grunt deploy:init

The staging site is hosted on heroku: http://pebblecode-staging.herokuapp.com/

To push the master branch to staging, run:

grunt deploy:staging

Or if you want a particular branch, run:

grunt deploy:staging --branch branch-name

where branch-name is the branch you want to push.

If there are errors with the push eg, error: failed to push some refs, you can add the --force flag eg,

grunt deploy:staging --force

To check the username/password (HTTP_USERNAME/HTTP_PASSWORD respectively)

heroku config --app pebblecode-staging

To change the username/password

heroku config:add HTTP_USERNAME=name --app pebblecode-staging
heroku config:add HTTP_PASSWORD=pass --app pebblecode-staging

It was initialised with

heroku config:add ENV=staging --app pebblecode-staging

The production site is hosted on github pages: http://pebblecode.com/, with files hosted at https://github.com/pebblecode/pebblecode.github.io

The deploy to production, run

grunt deploy:production

By default, it checks for uncommitted files, and won't allow you to proceed unless you commit/stash existing changes. To bypass this, use --force.

The grunt task does the following:

1. Copies files from dist to temp/production (which is a clone of https://github.com/pebblecode/pebblecode.github.io from grunt deploy:init)
2. Pushes to the production master branch, which should automatically be deployed to github