theme-juice 0.3.5 → 0.3.6
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +4 -2
- data/lib/theme-juice/executor.rb +4 -4
- data/lib/theme-juice/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 14a55344890082145f066a7f5a2145806b6f5c11
|
4
|
+
data.tar.gz: 82094878e10f5519dc216a7ff4810ec7f29f3290
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 0652f70940144ca95ff7e32315cd3829978e48400af45fc7536d9ca7593e172b48ce8e7d2b6a8e8907e04eda8274db2f410b9bba6d9b54fdf77c8ae22fcf516c
|
7
|
+
data.tar.gz: dee31bc5b85a9a822763d6082f6906be6e73abe41b2b4592f3734444f601110b1d495c49224bb86fd5027e78f55a4a46ba9648085f1188165a7abc7079d9bc0f
|
data/README.md
CHANGED
@@ -1,5 +1,5 @@
|
|
1
1
|
# Theme Juice [![Gem Version](https://badge.fury.io/rb/theme-juice.svg)](http://badge.fury.io/rb/theme-juice)
|
2
|
-
|
2
|
+
What is it? Theme Juice is a command line interface created to scaffold out a new WordPress development environment (using [VVV](https://github.com/Varying-Vagrant-Vagrants/VVV)) and countless development sites. Everybody loves one command setups, and `tj` can even do one command deployments too.
|
3
3
|
|
4
4
|
## Installation
|
5
5
|
* First, install [Vagrant](https://www.vagrantup.com/) and [VirtualBox](https://www.virtualbox.org/) for local development.
|
@@ -8,7 +8,9 @@ Command line interface to scaffold out a new WordPress development environment a
|
|
8
8
|
That`s it!
|
9
9
|
|
10
10
|
## Config
|
11
|
-
Because everybody likes to use different tools, you can create a `tj-config.yml` file that will house all of your theme-specific commands. This allows you to use a streamlined set of commands that will act as aliases to your per-project configuration.
|
11
|
+
Because everybody likes to use different tools, you can create a `tj-config.yml` file that will house all of your theme-specific commands. This allows you to use a streamlined set of commands that will act as aliases to your per-project configuration.
|
12
|
+
|
13
|
+
If you're into [Grunt](https://github.com/gruntjs/grunt), then use it. Prefer [Guard](https://github.com/guard/guard)? Go right ahead. This is obviously relative to the starter theme you use, since you can't exactly use Grunt with a starter theme that doesn't support it. Below is the config that comes baked into [our starter theme](https://github.com/ezekg/theme-juice-starter):
|
12
14
|
|
13
15
|
```yml
|
14
16
|
watch: bundle exec guard
|
data/lib/theme-juice/executor.rb
CHANGED
@@ -453,10 +453,10 @@ module ThemeJuice
|
|
453
453
|
# @return {Void}
|
454
454
|
###
|
455
455
|
def setup_config(config_path)
|
456
|
-
watch = ask "
|
457
|
-
server = ask "
|
458
|
-
vendor = ask "
|
459
|
-
install = ask "
|
456
|
+
watch = ask " ○ Watch command to use :", :blue, default: "bundle exec guard"
|
457
|
+
server = ask " ○ Deployment command to use :", :blue, default: "bundle exec cap"
|
458
|
+
vendor = ask " ○ Vendor command to use :", :blue, default: "composer"
|
459
|
+
install = ask " ○ Commands to run on theme install :", :blue, default: "composer install"
|
460
460
|
|
461
461
|
File.open "#{config_path}/tj-config.yml", "w" do |file|
|
462
462
|
file.puts "watch: #{watch}"
|
data/lib/theme-juice/version.rb
CHANGED