theme-juice 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: dc35777e4bd07bd8eae2a314ec39c251f5fa5562
-  data.tar.gz: 989ba458f6709aaa228889afa7198a6d51988e48
+  metadata.gz: 13028727bc3d7b0d809e5be56abab24dbb6406ed
+  data.tar.gz: 2bce67655374ac66c52c61664568fee1cd2e7c23
 SHA512:
-  metadata.gz: 6f88be099cb1768bd1d94a1af73a012353d65ce0946c5e7af354abe0178540d099ac69bef543ecef87d75c7569080c2db3f705823f23de792a99ac4de099d8b8
-  data.tar.gz: 8997b53e9b08991187e6a19b123a0f40fccf0cd81f7a846bab977b3ec672b7ddf4b974ee6a92386da5e0418783370b1178084a2a569fe729989c5ff2fb87cfd5
+  metadata.gz: eb1980616eebc102f4b54f9cba994a07ecdf06ec92d98cf9a78944de8545988810d640e0e3f01940fd42bb543d2c215d0c442056fa5b4810346fdf053750e0f2
+  data.tar.gz: 3c2daab95cabc9c8911a50fad390920c11e12978d81094de7174d422f0b108239dbec2599029198a04065b404139419d288495856ccb21fee7f52f53523cd7ed

data/README.md

@@ -1,80 +1,80 @@
-# Theme Juice
-Command line interface to scaffold out a new WordPress development environment and countless sites. Everybody loves one command setups, and 'tj' even does one command deployments too.
+# Theme Juice [![Gem Version](https://badge.fury.io/rb/theme-juice.svg)](http://badge.fury.io/rb/theme-juice)
+Command line interface to scaffold out a new WordPress development environment and countless sites. Everybody loves one command setups, and `tj` even does one command deployments too.
 
 ## Installation
 * First, install [Vagrant](https://www.vagrantup.com/) and [VirtualBox](https://www.virtualbox.org/) for local development.
-* Then, install [Composer](https://getcomposer.org/) and [WP-CLI](http://wp-cli.org/). _Make sure that these are executable from the command line._
-* Finally, you can run: '$ gem install theme-juice-cli'
+* Then, install [Composer](https://getcomposer.org/) and [WP-CLI](http://wp-cli.org/) (make sure they're executable).
+* Finally, you can run: `$ gem install theme-juice-cli`
 
-That's it!
+That`s it!
 
 ## Usage
 
 #### List available commands:
-List all commands for 'tj'.
-'''bash
+List all commands for `tj`.
+```bash
 tj
-'''
+```
 
 #### Setup VVV:
 This command will _only_ setup [Varying Vagrant Vagrants](https://github.com/Varying-Vagrant-Vagrants/VVV). It will not prompt you to create a new site. _Note: This is automatically run when you create your first site._
-'''bash
+```bash
 tj init
-'''
+```
 
 #### Create a new development site:
-Use this to create a new development site. It will automagically set up your entire development environment, including a local development site at 'http://<sites-dev-url>.dev' with WordPress installed and a fresh WP database. It will sync up your local site installation with the Vagrant VM. This task will also install and configure Vagrant/VVV into your '~/' directory if it has not already been installed. Site name is optional, as it will be asked for if not given.
-'''bash
+Use this to create a new development site. It will automagically set up your entire development environment, including a local development site at `http://<sites-dev-url>.dev` with WordPress installed and a fresh WP database. It will sync up your local site installation with the Vagrant VM. This task will also install and configure Vagrant/VVV into your `~/` directory if it has not already been installed. Site name is optional, as it will be asked for if not given.
+```bash
 tj create [<site-name>]
-'''
+```
 
 #### Setup an existing site:
-Use this to setup an existing local site installation within the development environment. You will go through the setup process to create the necessary files for the VM, including 'vvv-hosts', 'vvv-nginx.conf', and a fresh database (unless one already exists by the name chosen). Site name is optional, as it will be asked for if not given.
-'''bash
+Use this to setup an existing local site installation within the development environment. You will go through the setup process to create the necessary files for the VM, including `vvv-hosts`, `vvv-nginx.conf`, and a fresh database (unless one already exists by the name chosen). Site name is optional, as it will be asked for if not given.
+```bash
 tj setup [<site-name>] # Alias for 'tj create [<site-name>] --bare'
-'''
+```
 
 #### Delete a site from the VM: _(Does not remove your local site)_
-Use this to remove a site from your development environment. This is only remove files that were generated by 'tj'. including the database setup, development url, and shared directories. _It will not touch your local files._
-'''bash
+Use this to remove a site from your development environment. This is only remove files that were generated by `tj`. including the database setup, development url, and shared directories. _It will not touch your local files._
+```bash
 tj delete <site-name>
-'''
+```
 
 #### List all sites in the VM:
-Use this to list all sites within your development environment that were generated by 'tj'.
-'''bash
+Use this to list all sites within your development environment that were generated by `tj`.
+```bash
 tj list
-'''
+```
 
 #### Watch and compile assets: _(Guard)_
 Use this to watch and compile assets with [Guard](https://github.com/guard/guard). This is simply a wrapper for Guard commands.
-'''bash
+```bash
 tj watch # Alias for 'bundle exec guard #{cmd}'
-'''
+```
 
 #### Use for managing development environment: _(Vagrant)_
 Use this to easily manage your [Varying Vagrant Vagrants](https://github.com/Varying-Vagrant-Vagrants/VVV) development environment. This is simply a wrapper for Vagrant commands.
-'''bash
+```bash
 tj vm # Alias for 'cd ~/vagrant && vagrant #{cmd}'
-'''
+```
 
 #### Use for managing vendor dependencies: _(Composer)_
 Use this to easily manage your [Composer](https://github.com/composer/composer) dependencies. This is simply a wrapper for Composer commands.
-'''bash
+```bash
 tj vendor # Alias for 'composer #{cmd}'
-'''
+```
 
 #### Use for managing deployment and migration: _(Capistrano)_
 Use this to easily manage your deployment and migration with [Capistrano](https://github.com/capistrano/capistrano). This is simply a wrapper for Capistrano commands.
-'''bash
+```bash
 tj server # Alias for 'bundle exec cap #{cmd}'
-'''
+```
 
 ## Contributing
 
 1. First, create an [issue](https://github.com/ezekg/theme-juice-cli/issues) for your proposed feature. If it's a bug fix, go right to step 2.
 2. [Fork the repository](https://github.com/ezekg/theme-juice-cli/fork).
-3. Create a new feature branch. ('git checkout -b my-new-feature')
-4. Commit your changes. ('git commit -am 'Add some feature'')
-5. Push to the new branch. ('git push origin my-new-feature')
+3. Create a new feature branch. (`git checkout -b my-new-feature`)
+4. Commit your changes. (`git commit -am `Add some feature``)
+5. Push to the new branch. (`git push origin my-new-feature`)
 6. Create a new Pull Request.

data/lib/theme-juice/scaffold.rb

@@ -80,7 +80,7 @@ module ThemeJuice
                         say set_color(success, :yellow)
                         say "\n"
                         say "Success!".center(48), :green
-                        say "\n"
+                        say "\n\n"
 
                         # Output setup info
                         say "Here's your installation info:", :yellow

data/lib/theme-juice/version.rb

@@ -1,3 +1,3 @@
 module ThemeJuice
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: theme-juice
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Ezekiel Gabrielse