theme-juice 0.12.0 → 0.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2caab119d7f4e084b6430b0096fb091571df09bb
-  data.tar.gz: 656de710741b965747acf271547e2a6423a6a1e1
+  metadata.gz: 3da436c1899c43d49e6c60060ca315c566012697
+  data.tar.gz: fda413bca1b40ce1c21605bc4dc741f04a51433a
 SHA512:
-  metadata.gz: c8ed6de8ce066bdef5f2203a922d7447d41bdedba34f29d87c17c4628ce2fa087e5ccb37ebecec33dcc009429e360cc62844a2b105bfffa4d2270f3c07b48e41
-  data.tar.gz: d9fd6b3ab9f391efb182b5ec2f5f63f7812754ffc14ffe8e9ef3fd92eb9553b9ed8d84d2b67356682d932c170fc22a74afbe8652ecabcc110edcf8087d11a148
+  metadata.gz: ae1f99aa474c1b1fe6e3e2f95248a123916473348a5e2d8f4f45b0e04f98887b3081c81235215a687be1a3f4a0a185300b5c21628c2f4c985e30f212ffa51d2a
+  data.tar.gz: f3e72b175c8e09f154a3d6a69901457d21d0339c60084de7055cebdcc016ef0acd8a9462783e96ec3ceb86d0afcb88c88e609c66daba7fa12d752654bf3b5f6b

data/README.md

@@ -7,7 +7,11 @@
 
 ![Theme Juice CLI](demo.gif)
 
-_The master branch contains features currently in development, so don't expect it to work at all times. Grab the newest RubyGem instead of building directly from master._
+***The master branch contains features currently in development, so don't expect it to work at all times. Grab the newest RubyGem instead of building directly from master. Until `1.0`, we'll most likely be adjusting things, and that means breaking changes. Before updating, be sure to check back here to make sure that nothing major has changed.***
+
+_All breaking changes will go up a minor version (`0.x.0`), while patches and backwards compatible changes will bump up the patch number (`0.0.x`). After `1.0`, we will follow [semantic versioning](http://semver.org/)_.
+
+_On that note, as of `0.12`, we have renamed all mentions of "theme" to "template" (to avoid confusion, since these are application templates, and not just WordPress themes), and we have also renamed the default directory where `tj` installs the virtual machine to `~/tj-vagrant` to avoid possible conflicts with existing Vagrant installations._
 
 ## What is it?
 [Theme Juice CLI](http://themejuice.it) (`tj`) is a command line utility that allows you to generate, manage and deploy new local WordPress development applications in seconds using Vagrant, utilizing an Apache fork of [VVV](https://github.com/Varying-Vagrant-Vagrants/VVV) called [VVV-Apache](https://github.com/ezekg/theme-juice-vvv) as the virtual machine.
@@ -49,7 +53,7 @@ tj create
   * `wp-cli.local.yml` containing VM paths
 1. `tj` will provision the VM to put the new configuration into effect.
 
-If you've never used `tj` before, the that last step might take awhile. After that's done, you should be able to access your new project at the specified url. It's that easy!
+If you've never used `tj` before, then that last step might take awhile. After that's done, you should be able to access your new project at the specified url. It's that easy!
 
 ### Set up an existing project
 This sets up an existing local project within the development environment. You will go through a series of prompts to create the necessary files. This command is essentially an alias for `tj create --bare`.
@@ -158,7 +162,7 @@ Yes and no; in order for `tj` to properly create a project, the Vagrant box need
 [It's a file that contains custom rules to add into the main `Vagrantfile`, without actually having to modify it](https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/Vagrantfile#L208-L218). This allows us to easily modify the Vagrant box without causing merge conflicts if you were to update the VM source via `git pull`. Every file that `tj` modifies is _meant to be modified_, so at any time you may update your installation of VVV with a simple `git pull` without getting merge conflicts out the wazoo.
 
 ### What is a `Juicefile`?
-A YAML configuration file (`Juicefile`) can be used to store commonly-used build scripts. Each command block sequence can be mapped to an individual project's build tool, allowing a streamlined set of commands to be used across multiple projects that utilize different tools. In the near-future, this will also house your deployment configuration.
+A YAML configuration file called `Juicefile` can be used to store commonly-used build scripts, similar to [npm scripts](https://docs.npmjs.com/misc/scripts). Each command block sequence can be mapped to an individual project's build script, allowing a streamlined set of commands to be used across multiple projects that utilize different tools. In the near-future, this will also house your deployment configuration.
 
 Below is the config that comes baked into [our starter template](https://github.com/ezekg/theme-juice-starter):
 
@@ -253,16 +257,17 @@ Check out [capistrano-slackify](https://github.com/onthebeach/capistrano-slackif
 ## Troubleshooting
 
 1. [Help! It won't let me `git clone` anything!](#help-it-wont-let-me-git-clone-anything)
-1. [What the heck is an `invalid multibyte char (US-ASCII)`](#what-the-heck-is-an-invalid-multibyte-char-us-ascii)
+1. [What the heck is an `invalid multibyte char (US-ASCII)`?!](#what-the-heck-is-an-invalid-multibyte-char-us-ascii)
+1. [Why are my `.dev` domains resolving to `127.0.53.53`?!](#why-are-my-dev-domains-resolving-to-12705353)
 
 ### Help! It won't let me `git clone` anything!
 If you're hitting issues related to `git clone`, either cloning the VM or a starter template, then you most likely don't have [SSH-keys for GitHub set up correctly](https://help.github.com/articles/error-permission-denied-publickey/). Either go through that article and assure that you can use Git with the `git@github.com` protocol, or else you can manually run `tj` with the appropriate flags corresponding to the problem-repository, swapping out `git@github.com:` for `https://github.com/`. For example:
 
 ```
-tj create --template https://github.com/theme/repository.git --vm-box https://github.com/vm-box/repository.git
+tj create --template https://github.com/starter-template/repository.git --vm-box https://github.com/vm-box/repository.git
 ```
 
-This replaces the starter template and VM box repository URLs to use `https://` instead of the `git@` protocol.
+The flag duo above replaces the URLs for the starter template and VM box repositories so that they use `https` instead of the `git` protocol.
 
 ### What the heck is an `invalid multibyte char (US-ASCII)`?!
 For one reason or another, your terminal probably doesn't support UTF-8, so it's throwing a fit. Use the `--no-unicode` flag to disable the unicode characters. If the problem still persists, try running it with the `--boring` flag. That should disable all unicode characters and coloring.
@@ -271,6 +276,17 @@ For one reason or another, your terminal probably doesn't support UTF-8, so it's
 tj create --no-unicode # Or: tj create --boring
 ```
 
+### Why are my `.dev` domains resolving to `127.0.53.53`?!
+[Google has applied for control of the `.dev` TLD (top level domain)](https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1339). To fix it, you'll need to periodically flush your local DNS cache (I'm honestly not entirely sure why). In the future, we'll probably switch to something like `.localhost`. Here are a few commands to flush your cache on OSX:
+
+```bash
+# Yosemite:
+sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
+
+# Mountain Lion:
+sudo discoveryutil mdnsflushcache; sudo discoveryutil udnsflushcaches
+```
+
 _Still having issues? [Yell at me!](https://github.com/ezekg/theme-juice-cli/issues)_
 
 ## Contributing

data/lib/theme-juice/man/tj

@@ -147,7 +147,7 @@ Backup project
 Manage and run project tests
 .
 .SH "CONFIG FILE"
-A YAML Juicefile(5) configuration can be used to store commonly\-used build scripts\. Each command block sequence can be mapped to an individual project\'s build tool, allowing a streamlined set of commands to be used across multiple projects that utilize different tools\.
+A YAML Juicefile(5) configuration can be used to store commonly\-used build scripts, similar to npm(1) scripts\. Each command block sequence can be mapped to an individual project\'s build tool, allowing a streamlined set of commands to be used across multiple projects that utilize different tools\.
 .
 .TP
 \fBcommands\fR

data/lib/theme-juice/man/tj-create

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "TJ\-CREATE" "1" "July 2015" "" "Theme Juice Manual"
+.TH "TJ\-CREATE" "1" "August 2015" "" "Theme Juice Manual"
 .
 .SH "NAME"
 \fBtj\-create\fR \- Create a new project
@@ -10,7 +10,7 @@
 \fBtj create\fR [\-\-flag=\fIarg\fR] [\-\-flag]
 .
 .SH "DESCRIPTION"
-Creates a new project\. It will lead you through a series of prompts to set up required project information, such as name, location, theme, database info, etc\. Using the specified information, it will run the installation process and set up a local development environment, if one hasn\'t already been set up\. It will sync your local project location with the project location within the VM\.
+Creates a new project\. It will lead you through a series of prompts to set up required project information, such as name, location, template, database info, etc\. Using the specified information, it will run the installation process and set up a local development environment, if one hasn\'t already been set up\. It will sync your local project location with the project location within the VM\.
 .
 .SH "GLOBAL OPTIONS"
 .
@@ -23,8 +23,8 @@ Name of the project
 Location of the local project
 .
 .TP
-\fB\-t\fR, \fB\-\-theme\fR=\fIrepository\fR
-Starter theme to install
+\fB\-t\fR, \fB\-\-template\fR=\fIrepository\fR
+Starter template to install
 .
 .TP
 \fB\-u\fR, \fB\-\-url\fR=\fIurl\fR
@@ -39,8 +39,8 @@ Initialize a new git(1) remote repository
 Import an existing database
 .
 .TP
-\fB\-\-bare\fR, \fB\-\-no\-theme\fR
-Create a project without a starter theme
+\fB\-\-bare\fR, \fB\-\-no\-template\fR
+Create a project without a starter template
 .
 .TP
 \fB\-\-skip\-repo\fR

data/lib/theme-juice/man/tj-create.txt

@@ -10,7 +10,7 @@ SYNOPSIS
 
 DESCRIPTION
        Creates	a new project. It will lead you through a series of prompts to
-       set up required project information, such  as  name,  location,	theme,
+       set up required project information, such as name, location,  template,
        database  info,	etc.  Using the specified information, it will run the
        installation process and set up a local development environment, if one
        hasn't  already	been  set up. It will sync your local project location
@@ -23,8 +23,8 @@ GLOBAL OPTIONS
        -l, --location=path
 	      Location of the local project
 
-       -t, --theme=repository
-	      Starter theme to install
+       -t, --template=repository
+	      Starter template to install
 
        -u, --url=url
 	      Development URL for the project
@@ -35,8 +35,8 @@ GLOBAL OPTIONS
        -i, --import-db=path
 	      Import an existing database
 
-       --bare, --no-theme
-	      Create a project without a starter theme
+       --bare, --no-template
+	      Create a project without a starter template
 
        --skip-repo
 	      Skip repository prompts and use default settings
@@ -56,4 +56,4 @@ GLOBAL OPTIONS
 
 
 
-				   July 2015			  TJ-CREATE(1)
+				  August 2015			  TJ-CREATE(1)

data/lib/theme-juice/man/tj-deploy

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "TJ\-DEPLOY" "1" "July 2015" "" "Theme Juice Manual"
+.TH "TJ\-DEPLOY" "1" "August 2015" "" "Theme Juice Manual"
 .
 .SH "NAME"
 \fBtj\-deploy\fR \- Deploy a project
@@ -137,7 +137,7 @@ Relative path from deploy path to the tmp folder
 .
 .TP
 \fBdeployment\.stages\.<stage>\.shared\fR
-Sequence of relative files from application root to place inside of the shared folder
+Sequence of relative files from application root to place inside of the shared folder\. Files that end with a trailing forward slash are assumed to be a directory\.
 .
 .TP
 \fBdeployment\.stages\.<stage>\.roles\fR

data/lib/theme-juice/man/tj-deploy.txt

@@ -121,13 +121,14 @@ CONFIG FILE
 
        deployment.stages.<stage>.shared
 	      Sequence of relative files from application root to place inside
-	      of the shared folder
+	      of the shared folder. Files that end  with  a  trailing  forward
+	      slash are assumed to be a directory.
 
        deployment.stages.<stage>.roles
 	      Sequence of deployment roles for the stage
 
        deployment.stages.vagrant
-	      Required development environment settings; these	are  used  for
+	      Required	development  environment  settings; these are used for
 	      database and file migration
 
        deployment.stages.vagrant.server
@@ -160,4 +161,4 @@ CONFIG FILE
 
 
 
-				   July 2015			  TJ-DEPLOY(1)
+				  August 2015			  TJ-DEPLOY(1)

data/lib/theme-juice/man/tj.txt

@@ -121,9 +121,10 @@ CONFIG COMMANDS
 
 CONFIG FILE
        A  YAML	Juicefile(5)  configuration can be used to store commonly-used
-       build scripts. Each command block sequence can be mapped to an individ-
-       ual  project's build tool, allowing a streamlined set of commands to be
-       used across multiple projects that utilize different tools.
+       build scripts, similar to npm(1) scripts. Each command  block  sequence
+       can be mapped to an individual project's build tool, allowing a stream-
+       lined set of commands to be used across multiple projects that  utilize
+       different tools.
 
        commands
 	      Collection of various command block sequences
@@ -152,7 +153,7 @@ CONFIG FILE
        commands.test
 	      Command used to manage and run project tests
 
-       Placeholder arguments can be used within any command block sequence  to
+       Placeholder  arguments can be used within any command block sequence to
        allow splat or indexed arguments to be passed to the corresponding com-
        mand when executed.
 
@@ -162,8 +163,8 @@ CONFIG FILE
        %argN%, %argumentN%
 	      Where n is the argument index e.g. cmd %arg1% | cmd %arg2%
 
-       When naming your configuration file, use the recommended Juicefile,  or
-       .tj.yaml  naming convention. The raw filename regex matcher is below if
+       When  naming your configuration file, use the recommended Juicefile, or
+       .tj.yaml naming convention. The raw filename regex matcher is below  if
        you want to be a little different.
 
        /^(((\.)?(tj)|((J|j)uicefile))(\.y(a)?ml)?$)/
@@ -171,7 +172,7 @@ CONFIG FILE
 ENVIRONMENT
        All of the global options have a corresponding ENV variable that can be
        set to permanently use the specified value each time tj(1) is run. This
-       is useful if you're using an alternate vagrant(1) box, or if  you  need
+       is  useful  if you're using an alternate vagrant(1) box, or if you need
        to disable certain features due to limited support e.g. on Windows.
 
        TJ_VM_BOX=repository
@@ -187,7 +188,7 @@ ENVIRONMENT
 	      Force directory prefix for project in VM
 
        TJ_YOLO=bool
-	      Say  yes	to  anything  and everything, and maybe even get a few
+	      Say yes to anything and everything, and maybe  even  get	a  few
 	      surprises
 
        TJ_BORING=bool

data/lib/theme-juice/tasks/capistrano/rsync.rb

@@ -35,5 +35,11 @@ namespace :rsync do
         fetch(:linked_files).each { |f| execute :touch, shared_path.join(f) }
       end
     end
+
+    before "deploy:check:linked_dirs", :dirs do
+      on roles(:app) do
+        fetch(:linked_dirs).each { |f| execute :mkdir, "-p", shared_path.join(f) }
+      end
+    end
   end
 end

data/lib/theme-juice/tasks/settings.rb

@@ -24,7 +24,8 @@ module ThemeJuice
           set :application,  @config.deployment.application.name
 
           set :linked_files, fetch(:linked_files, []).concat(fetch(:shared_files, []))
-          set :linked_dirs,  fetch(:linked_dirs, []).push(fetch(:uploads_dir, ""))
+          set :linked_dirs,  fetch(:linked_dirs, []).concat(fetch(:shared_dirs, []))
+             .push(fetch(:uploads_dir, ""))
 
           %w[settings repository].each do |task|
             @config.deployment.send(task).symbolize_keys.each do |key, value|

data/lib/theme-juice/tasks/stage.rb

@@ -30,7 +30,8 @@ module ThemeJuice
         set :deploy_to,    -> { @stage.path }
         set :stage_url,    -> { @stage.url }
         set :uploads_dir,  -> { @stage.uploads }
-        set :shared_files, -> { @stage.shared }
+        set :shared_files, -> { @stage.shared.select { |f| !f.end_with? "/" } }
+        set :shared_dirs,  -> { @stage.shared.select { |f| f.end_with? "/" }.map { |f| f.chomp "/" } }
         set :tmp_dir,      -> { @stage.tmp }
         set :stage,        -> { @env.stage }
       end

data/lib/theme-juice/version.rb

@@ -1,5 +1,5 @@
 # encoding: UTF-8
 
 module ThemeJuice
-  VERSION = "0.12.0"
+  VERSION = "0.13.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: theme-juice
 version: !ruby/object:Gem::Version
-  version: 0.12.0
+  version: 0.13.0
 platform: ruby
 authors:
 - Ezekiel Gabrielse
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-18 00:00:00.000000000 Z
+date: 2015-08-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor