theme-juice 0.19.0 → 0.19.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/theme-juice/man/tj-deploy +2 -2
- data/lib/theme-juice/man/tj-deploy.txt +16 -15
- data/lib/theme-juice/tasks/invoke.rb +1 -1
- 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: 2ad42f0dafe50d14c526068af6c2d778ed37f7c5
|
|
4
|
+
data.tar.gz: 3f0d382aeaa8cfa8d322cf017281a1acf878ca56
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 5c2174b9e72f6fbcb8a67b56da5081d19fdbd142f35ed5aa05b2ec0a610ad32c551bb2b5d2296ff1f2d00508b884855cf93e667108ee36fdb483a29aeb7f01b3
|
|
7
|
+
data.tar.gz: 01b461d8e843f57051887b5fc05a66745a292ed0c7cb130040a992e2c618248244c3f03983483a770731dfda7dfcc7554b67428ed824fbf3e8b028acbbf0ffc5
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
.\" generated with Ronn/v0.7.3
|
|
2
2
|
.\" http://github.com/rtomayko/ronn/tree/0.7.3
|
|
3
3
|
.
|
|
4
|
-
.TH "TJ\-DEPLOY" "1" "
|
|
4
|
+
.TH "TJ\-DEPLOY" "1" "January 2016" "" "Theme Juice Manual"
|
|
5
5
|
.
|
|
6
6
|
.SH "NAME"
|
|
7
7
|
\fBtj\-deploy\fR \- Deploy a project
|
|
@@ -22,7 +22,7 @@ Follow these steps to quickly get up and running:
|
|
|
22
22
|
Create a \fBdeploy\fR user on the \fBstage\fR server
|
|
23
23
|
.
|
|
24
24
|
.IP "2." 4
|
|
25
|
-
|
|
25
|
+
Set up SSH keys for the new \fBdeploy\fR user to SSH in without a password
|
|
26
26
|
.
|
|
27
27
|
.IP "3." 4
|
|
28
28
|
Confirm the \fBdeploy\fR user owns the deploy path
|
|
@@ -21,7 +21,8 @@ SETUP
|
|
|
21
21
|
|
|
22
22
|
1. Create a deploy user on the stage server
|
|
23
23
|
|
|
24
|
-
2.
|
|
24
|
+
2. Set up SSH keys for the new deploy user to SSH in without a pass-
|
|
25
|
+
word
|
|
25
26
|
|
|
26
27
|
3. Confirm the deploy user owns the deploy path
|
|
27
28
|
|
|
@@ -47,7 +48,7 @@ PRIMARY COMMANDS
|
|
|
47
48
|
Rollback a previous deployment
|
|
48
49
|
|
|
49
50
|
setup, check
|
|
50
|
-
Run
|
|
51
|
+
Run a preliminary deployment check, making sure that all neces-
|
|
51
52
|
sary folders are created and accessible on the passed stage
|
|
52
53
|
|
|
53
54
|
SECONDARY COMMANDS
|
|
@@ -56,7 +57,7 @@ SECONDARY COMMANDS
|
|
|
56
57
|
the deployment.stages.vagrant.backup directory
|
|
57
58
|
|
|
58
59
|
db:pull
|
|
59
|
-
Pull
|
|
60
|
+
Pull the database from the passed stage and import it into the
|
|
60
61
|
development environment
|
|
61
62
|
|
|
62
63
|
db:push
|
|
@@ -64,7 +65,7 @@ SECONDARY COMMANDS
|
|
|
64
65
|
into the passed stage
|
|
65
66
|
|
|
66
67
|
env:pull
|
|
67
|
-
Pull
|
|
68
|
+
Pull the current .env.<stage> file from the passed stage to the
|
|
68
69
|
development environment
|
|
69
70
|
|
|
70
71
|
env:push
|
|
@@ -76,19 +77,19 @@ SECONDARY COMMANDS
|
|
|
76
77
|
the development environment
|
|
77
78
|
|
|
78
79
|
uploads:push
|
|
79
|
-
Push
|
|
80
|
+
Push the uploads folder from the development environment to the
|
|
80
81
|
passed stage's uploads folder
|
|
81
82
|
|
|
82
83
|
file:pull=path
|
|
83
|
-
Pull
|
|
84
|
+
Pull a relative file from the passed stage to the development
|
|
84
85
|
environment.
|
|
85
86
|
|
|
86
87
|
file:push=path
|
|
87
|
-
Push
|
|
88
|
+
Push a relative file from the development environment to the
|
|
88
89
|
passed stage.
|
|
89
90
|
|
|
90
91
|
dir:pull=path
|
|
91
|
-
Recursively
|
|
92
|
+
Recursively pull a relative directory from the passed stage to
|
|
92
93
|
the development environment.
|
|
93
94
|
|
|
94
95
|
dir:push=path
|
|
@@ -96,9 +97,9 @@ SECONDARY COMMANDS
|
|
|
96
97
|
ronment to the passed stage.
|
|
97
98
|
|
|
98
99
|
CONFIG FILE
|
|
99
|
-
The
|
|
100
|
-
ment-related
|
|
101
|
-
you
|
|
100
|
+
The YAML Juicefile(5) configuration may be used to store deploy-
|
|
101
|
+
ment-related settings. Below you will find the various block sequences
|
|
102
|
+
you may use to define your project's deployment settings. All of these
|
|
102
103
|
will be passed to capistrano(1) to invoke a deployment.
|
|
103
104
|
|
|
104
105
|
deployment
|
|
@@ -118,7 +119,7 @@ CONFIG FILE
|
|
|
118
119
|
rsync_<setting> during the deployment initialization
|
|
119
120
|
|
|
120
121
|
deployment.slack
|
|
121
|
-
Optional
|
|
122
|
+
Optional settings passed to capistrano-slackify(1); mapped as
|
|
122
123
|
slack_<setting> during the deployment initialization
|
|
123
124
|
|
|
124
125
|
deployment.stages
|
|
@@ -144,14 +145,14 @@ CONFIG FILE
|
|
|
144
145
|
|
|
145
146
|
deployment.stages.<stage>.shared
|
|
146
147
|
Sequence of relative files from application root to place inside
|
|
147
|
-
of
|
|
148
|
+
of the shared folder. Files that end with a trailing forward
|
|
148
149
|
slash are assumed to be a directory.
|
|
149
150
|
|
|
150
151
|
deployment.stages.<stage>.roles
|
|
151
152
|
Sequence of deployment roles for the stage
|
|
152
153
|
|
|
153
154
|
deployment.stages.vagrant
|
|
154
|
-
Required
|
|
155
|
+
Required development environment settings; these are used for
|
|
155
156
|
database and file migration
|
|
156
157
|
|
|
157
158
|
deployment.stages.vagrant.server
|
|
@@ -184,4 +185,4 @@ CONFIG FILE
|
|
|
184
185
|
|
|
185
186
|
|
|
186
187
|
|
|
187
|
-
|
|
188
|
+
January 2016 TJ-DEPLOY(1)
|
|
@@ -35,7 +35,7 @@ module ThemeJuice
|
|
|
35
35
|
else
|
|
36
36
|
@env.cap.invoke *args
|
|
37
37
|
end
|
|
38
|
-
rescue SSHKit::Runner::ExecuteError => err
|
|
38
|
+
rescue SSHKit::Command::Failed, SSHKit::Runner::ExecuteError => err
|
|
39
39
|
@env.cap.invoke "deploy:failed"
|
|
40
40
|
@io.error "Capistrano has encountered a fatal error", StandardError do
|
|
41
41
|
puts err.message.force_encoding "UTF-8"
|
data/lib/theme-juice/version.rb
CHANGED