theme-juice 0.1.2 → 0.1.3

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: d52c78f103373783f18718a99995d629cad4f2fb
4
- data.tar.gz: a700756fe35dd8eebf53d0381a2502fd5cc7fe88
3
+ metadata.gz: 4964da65fba7f6f253d08619b19586abf43665bc
4
+ data.tar.gz: 70d86b05315d3bfb93f82a48cf8ce7c633e7a974
5
5
  SHA512:
6
- metadata.gz: b1abf98f228790378b447d279cc99c90bab231b7a0ec2385ed6d344eb2f4056f8380eab59959e9932f431875136bd227fb9597ee6476068bb6b403b31486c75a
7
- data.tar.gz: 09e926f758aff262b986578c3f4d8790eb3b838ed44e644bd02f8c33223746ab2c8b604e5ea780d2e9668c3a48fdb92a6b18c7d9899e4a31054fd2b6f40d1c70
6
+ metadata.gz: e8793bb4a4d6823dd35984a6f9e435468c12f56175eaac2f33738015388606db66f29abc2d4d05e501e64984b20710e7116aaa07d10dfa425f2c6f2823ce3f5a
7
+ data.tar.gz: 29096f37c0136ea829cfe4996041823d96cabee04ae127d3823a70631f6baafd804340299bba268bcf91e27a564596fbdc2f63d1eae4f1bfc3cc3d259412c967
data/README.md CHANGED
@@ -25,19 +25,19 @@ tj init
25
25
  #### Create a new development site:
26
26
  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.
27
27
  ```bash
28
- tj create [<site-name>]
28
+ tj create [<SITE-NAME>]
29
29
  ```
30
30
 
31
31
  #### Setup an existing site:
32
32
  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.
33
33
  ```bash
34
- tj setup [<site-name>] # Alias for 'tj create [<site-name>] --bare'
34
+ tj setup [<SITE-NAME>] # Alias for 'tj create [<SITE-NAME>] --bare'
35
35
  ```
36
36
 
37
37
  #### Delete a site from the VM: _(Does not remove your local site)_
38
38
  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._
39
39
  ```bash
40
- tj delete <site-name>
40
+ tj delete <SITE-NAME>
41
41
  ```
42
42
 
43
43
  #### List all sites in the VM:
@@ -49,25 +49,34 @@ tj list
49
49
  #### Watch and compile assets: _(Guard)_
50
50
  Use this to watch and compile assets with [Guard](https://github.com/guard/guard). This is simply a wrapper for Guard commands.
51
51
  ```bash
52
- tj watch # Alias for 'bundle exec guard #{cmd}'
52
+ tj watch # Alias for 'bundle exec guard [COMMANDS]'
53
53
  ```
54
54
 
55
55
  #### Use for managing development environment: _(Vagrant)_
56
56
  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.
57
57
  ```bash
58
- tj vm # Alias for 'cd ~/vagrant && vagrant #{cmd}'
58
+ tj vm # Alias for 'cd ~/vagrant && vagrant [COMMANDS]'
59
59
  ```
60
60
 
61
61
  #### Use for managing vendor dependencies: _(Composer)_
62
62
  Use this to easily manage your [Composer](https://github.com/composer/composer) dependencies. This is simply a wrapper for Composer commands.
63
63
  ```bash
64
- tj vendor # Alias for 'composer #{cmd}'
64
+ tj vendor # Alias for 'composer [COMMANDS]'
65
65
  ```
66
66
 
67
67
  #### Use for managing deployment and migration: _(Capistrano)_
68
68
  Use this to easily manage your deployment and migration with [Capistrano](https://github.com/capistrano/capistrano). This is simply a wrapper for Capistrano commands.
69
69
  ```bash
70
- tj server # Alias for 'bundle exec cap #{cmd}'
70
+ tj server # Alias for 'bundle exec cap [COMMANDS]'
71
+ ```
72
+
73
+ #### Executing WP-CLI locally inside your VM with `wp-cli-ssh`
74
+ You can run `wp` commands locally if you specify a `--host`. Upon setup, an `ssh` block for the VM is automatically added to the `wp-cli.yml` file with all of your development environment paths.
75
+ ```bash
76
+ wp ssh --host=vagrant [COMMANDS]
77
+
78
+ # Create an alias
79
+ alias wpv="wp ssh --host=vagrant"
71
80
  ```
72
81
 
73
82
  ## Contributing
@@ -306,6 +306,7 @@ module ThemeJuice
306
306
  def setup_wildcard_subdomains
307
307
  say "Setting up wildcard subdomains...", :yellow
308
308
  open File.expand_path("~/vagrant/Vagrantfile"), "a+" do |file|
309
+ file.puts "\n"
309
310
  file.puts "###"
310
311
  file.puts "# Enable wildcard subdomains"
311
312
  file.puts "#"
@@ -454,7 +455,7 @@ module ThemeJuice
454
455
  file.puts "# This block is automatically generated by ThemeJuice. Do not edit."
455
456
  file.puts "###"
456
457
  file.puts "Vagrant.configure('2') do |config|"
457
- file.puts "\tconfig.vm.synced_folder '#{@opts[:site_location]}', '/srv/www/tj-#{@opts[:site_name]}', mount_options: ['dmode=777,fmode=777']"
458
+ file.puts "\tconfig.vm.synced_folder '#{@opts[:site_location]}', '/srv/www/tj-#{@opts[:site_name]}', mount_options: ['dmode=777','fmode=777']"
458
459
  file.puts "\tconfig.landrush.host '#{@opts[:dev_url]}', '192.168.50.4'"
459
460
  file.puts "end"
460
461
  file.puts "### End '#{@opts[:site_name]}'"
@@ -1,3 +1,3 @@
1
1
  module ThemeJuice
2
- VERSION = "0.1.2"
2
+ VERSION = "0.1.3"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: theme-juice
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.2
4
+ version: 0.1.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Ezekiel Gabrielse