capistrano-deploy 0.0.1 → 0.0.2
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.
- data/README.md +1 -6
- data/capistrano-deploy.gemspec +1 -1
- metadata +3 -3
data/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
Capistrano recipes
|
|
1
|
+
Capistrano deploy recipes
|
|
2
2
|
==================
|
|
3
3
|
|
|
4
4
|
Deploy
|
|
@@ -17,22 +17,18 @@ Minimal Capfile for deploy:
|
|
|
17
17
|
|
|
18
18
|
To setup:
|
|
19
19
|
|
|
20
|
-
!!!plain
|
|
21
20
|
cap deploy:setup
|
|
22
21
|
|
|
23
22
|
Then when you push some changes to git repository simply run:
|
|
24
23
|
|
|
25
|
-
!!!plain
|
|
26
24
|
cap deploy
|
|
27
25
|
|
|
28
26
|
If you have migrations instead of previous command run:
|
|
29
27
|
|
|
30
|
-
!!!plain
|
|
31
28
|
cap deploy:migrations
|
|
32
29
|
|
|
33
30
|
To look through changes to be deployed:
|
|
34
31
|
|
|
35
|
-
!!!plain
|
|
36
32
|
cap deploy:pending
|
|
37
33
|
|
|
38
34
|
Multistage
|
|
@@ -79,5 +75,4 @@ To automatically update crontab file:
|
|
|
79
75
|
|
|
80
76
|
You can also clear crontab file with command:
|
|
81
77
|
|
|
82
|
-
!!!plain
|
|
83
78
|
cap whenever:clear_crontab
|
data/capistrano-deploy.gemspec
CHANGED
metadata
CHANGED
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: capistrano-deploy
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
hash:
|
|
4
|
+
hash: 27
|
|
5
5
|
prerelease:
|
|
6
6
|
segments:
|
|
7
7
|
- 0
|
|
8
8
|
- 0
|
|
9
|
-
-
|
|
10
|
-
version: 0.0.
|
|
9
|
+
- 2
|
|
10
|
+
version: 0.0.2
|
|
11
11
|
platform: ruby
|
|
12
12
|
authors:
|
|
13
13
|
- Just Lest
|