theme-juice 0.9.0 → 0.9.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +6 -3
- data/lib/theme-juice/commands/create.rb +5 -5
- data/lib/theme-juice/project.rb +1 -1
- data/lib/theme-juice/tasks/apache.rb +1 -1
- data/lib/theme-juice/tasks/forward_ports.rb +1 -1
- data/lib/theme-juice/tasks/nginx.rb +1 -1
- data/lib/theme-juice/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: a37e3375104781691f2bec5e2465dc9a07f7431c
|
4
|
+
data.tar.gz: 8c00327c81bb1818cdab702d1ee4ee37a13c645e
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b66f0290a4eb84791966ccf993f810e98461ec55fce0c0dbe1864dc8089077796262bab865cacd18a19ca205def845388b17dd4789e1af8f40ce8a1219003347
|
7
|
+
data.tar.gz: a9430a8edcf945938778643382dc8bb4c8c380464b3d7c0ffde596dda7d18d4f03d5c6fd3ab84009998d50467e41c992c864941a9fca23d4b062b337edd60ee4
|
data/README.md
CHANGED
@@ -17,6 +17,8 @@ _This project is currently under active development and will not be completely '
|
|
17
17
|
|
18
18
|
I recommend one of the latest versions of Ruby MRI (2.2, 2.1, 2.0). `tj` requires at least MRI 1.9.3. For the full report, check out the [Travis CI build status](https://travis-ci.org/ezekg/theme-juice-cli), where I test against an array of Ruby interpreters.
|
19
19
|
|
20
|
+
I also recommend you set up [SSH-keys for GitHub](https://help.github.com/articles/generating-ssh-keys/). Internally, `tj` uses `git clone` with SSH URLs, [so things might break if you don't have your keys set up properly](#help-it-wont-let-me-git-clone-anything).
|
21
|
+
|
20
22
|
## Installation
|
21
23
|
```
|
22
24
|
gem install theme-juice
|
@@ -25,7 +27,7 @@ gem install theme-juice
|
|
25
27
|
## Getting Started
|
26
28
|
|
27
29
|
#### Create a new project
|
28
|
-
This 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
|
30
|
+
This 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
|
29
31
|
location within the VM, so you can run this from anywhere on your local system.
|
30
32
|
|
31
33
|
```
|
@@ -48,7 +50,7 @@ It will not touch your local folders that were synced to the VM.
|
|
48
50
|
tj delete
|
49
51
|
```
|
50
52
|
|
51
|
-
#### Want
|
53
|
+
#### Want more?
|
52
54
|
Want to check out all of the various flags and features `tj` offers? Just ask `tj` for help, and you'll be greeted with a nice `man` page full of information about how to use just about everything.
|
53
55
|
|
54
56
|
```
|
@@ -94,7 +96,7 @@ tj new --vm-box git@github.com:Varying-Vagrant-Vagrants/VVV.git --nginx
|
|
94
96
|
|
95
97
|
To use these permanently, set the appropriate `ENV` variables through your `.bashrc` or similar, i.e. `export TJ_VM_BOX=git@github.com:Varying-Vagrant-Vagrants/VVV.git` and `export TJ_NGINX=true`.
|
96
98
|
|
97
|
-
_Note: Before running this, you might want to either choose a new `vm-path`, or destroy any existing VMs inside of your `~/vagrant` directory. If `tj` detects a VM already installed, it will skip installing the new box._
|
99
|
+
_Note: Before running this, you might want to either choose a new `vm-path`, or destroy any existing VMs inside of your `~/vagrant` directory. If `tj` detects that a VM already installed, it will skip installing the new box._
|
98
100
|
|
99
101
|
#### So, does that mean I can use any Vagrant box?
|
100
102
|
Yes and no; in order for `tj` to properly create a project, the Vagrant box needs to follow the same directory structure as VVV, and include a `Customfile`. Here is the required structure that `tj` needs in order to be able to create new projects:
|
@@ -135,6 +137,7 @@ Below is the config that comes baked into [our starter theme](https://github.com
|
|
135
137
|
commands:
|
136
138
|
install:
|
137
139
|
- composer install
|
140
|
+
- bundler install
|
138
141
|
- npm install
|
139
142
|
- bower install
|
140
143
|
- grunt build
|
@@ -55,7 +55,7 @@ module ThemeJuice
|
|
55
55
|
@project.name = @opts.fetch("name") { name }
|
56
56
|
@project.location = @opts.fetch("location") { location }
|
57
57
|
@project.url = @opts.fetch("url") { url }
|
58
|
-
@project.
|
58
|
+
@project.xip_url = @opts.fetch("xip_url") { xip_url }
|
59
59
|
@project.theme = @opts.fetch("theme") { theme }
|
60
60
|
@project.repository = @opts.fetch("repository") { repository }
|
61
61
|
@project.db_host = @opts.fetch("db_host") { db_host }
|
@@ -125,10 +125,10 @@ module ThemeJuice
|
|
125
125
|
true
|
126
126
|
end
|
127
127
|
|
128
|
-
def
|
129
|
-
|
128
|
+
def xip_url
|
129
|
+
xip_url = @project.url.gsub /\.dev$/, ""
|
130
130
|
|
131
|
-
|
131
|
+
xip_url
|
132
132
|
end
|
133
133
|
|
134
134
|
def theme
|
@@ -146,7 +146,7 @@ module ThemeJuice
|
|
146
146
|
@io.say "This is a stock WordPress install, so things such as the '.env' file will not be set up. You'll need to input your database information manually after the setup.", {
|
147
147
|
:color => :yellow, :icon => :notice }
|
148
148
|
when /(other)/
|
149
|
-
THEMES[choice] = @io.ask "What is the repository URL
|
149
|
+
THEMES[choice] = @io.ask "What is the repository URL of the starter theme that you would like to clone?"
|
150
150
|
when /(none)/
|
151
151
|
@project.bare = true
|
152
152
|
@io.say "Next time you need to create a project without a starter theme, you can just run the 'setup' command instead.", {
|
data/lib/theme-juice/project.rb
CHANGED
@@ -33,7 +33,7 @@ module ThemeJuice
|
|
33
33
|
%Q{<VirtualHost *:80>
|
34
34
|
DocumentRoot #{@project.vm_srv}
|
35
35
|
ServerName #{@project.url}
|
36
|
-
ServerAlias *.#{@project.url} #{@project.
|
36
|
+
ServerAlias *.#{@project.url} #{@project.xip_url}.*.xip.io *.#{@project.xip_url}.*.xip.io
|
37
37
|
</VirtualHost>
|
38
38
|
|
39
39
|
}
|
@@ -32,7 +32,7 @@ config.vm.network "forwarded_port", guest: 443, host: 8443}
|
|
32
32
|
private
|
33
33
|
|
34
34
|
# @TODO I'd like to eventually support every OS. I'm only familiar with
|
35
|
-
# OSX, so that's why there's nothing else here
|
35
|
+
# OSX, so that's why there's nothing else here at the moment
|
36
36
|
def forward_host_ports
|
37
37
|
if OS.osx?
|
38
38
|
%Q{if defined? VagrantPlugins::Triggers
|
@@ -33,7 +33,7 @@ module ThemeJuice
|
|
33
33
|
%Q(server {
|
34
34
|
listen 80;
|
35
35
|
listen 443 ssl;
|
36
|
-
server_name .#{@project.url} ~(^|^[a-z0-9.-]*\\.)#{@project.
|
36
|
+
server_name .#{@project.url} ~(^|^[a-z0-9.-]*\\.)#{@project.xip_url}\\.\\d+\\.\\d+\\.\\d+\\.\\d+\\.xip\\.io$;
|
37
37
|
root #{@project.vm_srv};
|
38
38
|
include /etc/nginx/nginx-wp-common.conf;
|
39
39
|
}
|
data/lib/theme-juice/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: theme-juice
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.9.
|
4
|
+
version: 0.9.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Ezekiel Gabrielse
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2015-06-
|
11
|
+
date: 2015-06-17 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: thor
|