wp-capistrano 0.0.0 → 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- data/README.rdoc +36 -3
- data/Rakefile +1 -1
- data/VERSION +1 -1
- metadata +4 -4
data/README.rdoc
CHANGED
@@ -1,16 +1,49 @@
|
|
1
1
|
= wp-capistrano
|
2
2
|
|
3
|
+
Capistrano receipe for WordPress
|
4
|
+
|
3
5
|
== Usage
|
4
6
|
|
5
7
|
A sample Capfile and config.yml exist in lib/wp_generate/templates/capify.
|
6
8
|
|
7
|
-
Those should be copied into wp-content/Capfile and wp-content/lib/config.yml respectively.
|
9
|
+
Those should be copied into wp-content/Capfile and wp-content/lib/config.yml respectively. Things you'll need to change in config.yml include:
|
10
|
+
|
11
|
+
- application.repository -> set that to the repository that includes the contents of wp-content
|
12
|
+
- wordpress.repository -> in the sample this is set to our mirror on GitHub, but you may prefer to mirror that locally or set up your own
|
13
|
+
- wordpress.version -> a git tree-ish, which can be a branch name, tag, or a commit hash (e.g. v2.9.2)
|
14
|
+
- deploy.* -> these names are used when doing cap deploy when deploying to non-default environments (i.e. cap production deploy)
|
15
|
+
- deploy.*.ssh_user -> the user who will log into the machine, if omitted will use the default
|
16
|
+
- deploy.*.ssh_domain -> the host to be SSHed into
|
17
|
+
- deploy.*.path -> the path on the remote machine
|
18
|
+
- deploy.*.vhost -> the intended host name when being viewed on the remote machine
|
19
|
+
- deploy.*.database.*
|
8
20
|
|
9
|
-
For the initial run, you should first create the directory specified in deploy.*.path on the server, then run:
|
21
|
+
For the initial run, you should first create the directory specified in deploy.*.path on the server, or at least make sure it's possible for the deploy user to create it, then run:
|
10
22
|
|
11
23
|
cap setup:wordpress
|
12
24
|
|
13
|
-
This will
|
25
|
+
This will create the Capistrano structure, check out the specified version of WordPress, create a shared directory full of things like wp-config.php and uploads. Now go and edit wp-config.php on the server, unless you specified the database password in config.yml. Then to deploy your wp-content, run:
|
26
|
+
|
27
|
+
cap deploy
|
28
|
+
|
29
|
+
If you've set up Apache correctly (a .htaccess will be created, but that's all the help it will give you), you can visit the vhost you specified and everything should be working.
|
30
|
+
|
31
|
+
When you update things, don't forget to push wp-content (and any submodules), and:
|
32
|
+
|
33
|
+
cap deploy
|
34
|
+
|
35
|
+
And to setup/deploy to hosts other than the default, use:
|
36
|
+
|
37
|
+
cap staging deploy
|
38
|
+
cap production deploy
|
39
|
+
|
40
|
+
== Additional features
|
41
|
+
|
42
|
+
=== SASS
|
43
|
+
|
44
|
+
If there exists wp-content/themes/*/*/sass_output.php it will be executed (from that directory) and its contents will be placed in sass_output.css. Then ../style.css will be sedded to s/\.php/\.css/, and both will be uploaded to the appropriate places.
|
45
|
+
|
46
|
+
sass_output.php can be found in wp-generate's theme generator. It is very handy for development, but less server load is more good, so we "cache" it in this way.
|
14
47
|
|
15
48
|
== wp-generate
|
16
49
|
|
data/Rakefile
CHANGED
@@ -4,7 +4,7 @@ begin
|
|
4
4
|
require 'jeweler'
|
5
5
|
Jeweler::Tasks.new do |gem|
|
6
6
|
gem.name = "wp-capistrano"
|
7
|
-
gem.summary = %Q{Capistrano receipe
|
7
|
+
gem.summary = %Q{Capistrano receipe for WordPress}
|
8
8
|
gem.description = %Q{}
|
9
9
|
gem.email = "tom@thedextrousweb.com"
|
10
10
|
gem.homepage = "http://github.com/dxw/wp-capistrano"
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.
|
1
|
+
0.1.0
|
metadata
CHANGED
@@ -4,9 +4,9 @@ version: !ruby/object:Gem::Version
|
|
4
4
|
prerelease: false
|
5
5
|
segments:
|
6
6
|
- 0
|
7
|
+
- 1
|
7
8
|
- 0
|
8
|
-
|
9
|
-
version: 0.0.0
|
9
|
+
version: 0.1.0
|
10
10
|
platform: ruby
|
11
11
|
authors:
|
12
12
|
- The Dextrous Web
|
@@ -27,6 +27,7 @@ extensions: []
|
|
27
27
|
extra_rdoc_files:
|
28
28
|
- README.rdoc
|
29
29
|
files:
|
30
|
+
- README.rdoc
|
30
31
|
- Rakefile
|
31
32
|
- VERSION
|
32
33
|
- lib/wp_capistrano/deploy.rb
|
@@ -38,7 +39,6 @@ files:
|
|
38
39
|
- lib/wp_generate/generator/capify.rb
|
39
40
|
- lib/wp_generate/templates/capify/Capfile
|
40
41
|
- lib/wp_generate/templates/capify/config.yml
|
41
|
-
- README.rdoc
|
42
42
|
has_rdoc: true
|
43
43
|
homepage: http://github.com/dxw/wp-capistrano
|
44
44
|
licenses: []
|
@@ -68,6 +68,6 @@ rubyforge_project:
|
|
68
68
|
rubygems_version: 1.3.6
|
69
69
|
signing_key:
|
70
70
|
specification_version: 3
|
71
|
-
summary: Capistrano receipe
|
71
|
+
summary: Capistrano receipe for WordPress
|
72
72
|
test_files: []
|
73
73
|
|